| 1 |
Just because Memtest86 went 30% without failure does not mean your RAM is 30% OK. It should run for at least a full loop, and I typically run it for at least 2 loops (though only once have I seen a system suddenly start spewing errors it didn't have during the first loop, and I've run it on a lot of systems). It does take a while, so you probably don't want to sit around watching it. I usually let it run overnight while I sleep. |
| 2 |
|
| 3 |
|
| 4 |
----- Original Message ---- |
| 5 |
From: Peter Davoust <worldgnat@×××××.com> |
| 6 |
To: gentoo-amd64@l.g.o |
| 7 |
Sent: Monday, May 14, 2007 2:08:42 PM |
| 8 |
Subject: Re: [gentoo-amd64] Gentoo crashing? |
| 9 |
|
| 10 |
Ok, so I compiled a new kernel, and it seemed to work. I booted the new kernel, I was able to unzip and install dhcpcd, ndiswrapper, wireless-tools, and cab extract. Then, once the wireless was working, I tried emerge --search dhcpcd, because gentoo apparently doesn't like my manually configured dhcpcd.... CRASH! I ran memtest86+, as suggested, and it got to at least 30% without a failure. I'll try it again, but at least 30% of my memory is in tact. I'll try to emerge some other things, and see how it goes. |
| 11 |
|
| 12 |
|
| 13 |
-Peter |
| 14 |
|
| 15 |
On 5/14/07, dustin@×××××××.us <dustin@×××××××.us> wrote: |
| 16 |
On Mon, May 14, 2007 at 02:04:30AM -0400, Peter Davoust wrote: |
| 17 |
> Ok, first, while I appreciate your advice, this is a brand new laptop |
| 18 |
|
| 19 |
> and there's no way I'm running bonnie++ (that's prime95, right?), or |
| 20 |
> anything with the words "cpu" and "burn" in the same sentence on this |
| 21 |
> thing. Memtest86 might be an option as long as it has no potential to |
| 22 |
|
| 23 |
> kill anything. I agree, it could be the heat, and that was the first |
| 24 |
> thing that came to my mind, but Vista boots and runs for long periods |
| 25 |
> of time with no issues. I'll check it out with the new kernel in the |
| 26 |
|
| 27 |
> morning and see what it does. |
| 28 |
|
| 29 |
Any new laptop should have the hardware smarts not to smoke itself, or |
| 30 |
something really is broken. It may shut down "unexpectedly" (which I |
| 31 |
also consider a design bug), but actually causing damage is unlikely. |
| 32 |
|
| 33 |
|
| 34 |
That said, this really sounds like a RAM problem, so I would run |
| 35 |
memtest86 first. Memtest86 has zero chance of smoking any system that |
| 36 |
has passed a factory QA check. |
| 37 |
|
| 38 |
I had a Gentoo system (a server) that pretty much ran (to be honest, it |
| 39 |
|
| 40 |
was a heavily used database server that stayed up for a good 3 months in |
| 41 |
this state). However, its clock was skewed something like 10m/hour (I |
| 42 |
now think this was due to lost ticks during processing of memory |
| 43 |
|
| 44 |
faults). |
| 45 |
|
| 46 |
I tried all the various kernel flags, largemem, etc., only to find out |
| 47 |
that the problem was (as others on this thread have posted) incompatible |
| 48 |
RAM. I point this out only to say that bad RAM can cause *very* unusual |
| 49 |
|
| 50 |
problems (not just the segfaults you'd expect), and to say that lots of |
| 51 |
complex operations (like Vista, for example) can continue to run just |
| 52 |
fine in such a broken environment. |
| 53 |
|
| 54 |
Dustin |
| 55 |
-- |
| 56 |
|
| 57 |
gentoo-amd64@g.o mailing list |
Archives