On Wed, 2006-04-05 at 19:38 +1000, Nick Piggin wrote: > Ian Kumlien wrote: > > As i said, i really doubt that the memory is at fault here, it has done > > several passes over the memory but not all tests. I can give it a go > > though, but i really doubt it'll find anything. > > If it doesn't cost you much time (ie. do it overnight) it could save some > developers a lot of time. Well, the memory passes test 1-5 and 8. The 32 bit thingies all fail on 4 dimms, so either 4 dimms are broken or the test is broken for amd64. Anyways, i noticed that the memory clocking got skewed when all the memory was in the machine, so i've removed 1gb of memory. > > The kernel i run is a plain 2.6.16.1 from kernel.org (i have heard that > > you can actually compile gentoos own these days) > > OK, good. 2.6.16.2 now... And a new nvidia driver... -- Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
Attachment:
signature.asc
Description: This is a digitally signed message part
- References:
- Re: [OOPS] related to swap?
- From: Ian Kumlien <[email protected]>
- Re: [OOPS] related to swap?
- From: Nick Piggin <[email protected]>
- Re: [OOPS] related to swap?
- Prev by Date: Re: [PATCH] i386/x86-64: Return defined error value for bad PCI config space accesses
- Next by Date: Re: 2.6.17-rc1-mm2: badness in 3w_xxxx driver
- Previous by thread: Re: [OOPS] related to swap?
- Next by thread: [PATCH] Add a /proc/self/exedir link
- Index(es):
 |