| 1 |
Quoth Kevin (Tue 2004-05-18 04:29:58AM -0400): |
| 2 |
|
| 3 |
> On Thursday 13 May 2004 11:54, Greg KH wrote: |
| 4 |
> |
| 5 |
> > On Thu, May 13, 2004 at 07:06:12AM -0400, Kevin wrote: |
| 6 |
> > |
| 7 |
> > > Greg KH thinks it's bad memory, |
| 8 |
> > |
| 9 |
> > It's not only me, it's memtest86 saying it :) |
| 10 |
> |
| 11 |
> True. Although it is locking up after only 1-2 minutes of operation. |
| 12 |
> What conclusion should I draw from that? |
| 13 |
|
| 14 |
Bad system board. :( |
| 15 |
|
| 16 |
> Although I'm sure there are others here with more experience |
| 17 |
> troubleshooting such problems, I'm thinking that the above is enough to |
| 18 |
> base a pretty sound conclusion upon, and the conclusion I would draw is |
| 19 |
> that hardware and memory are not the cause of these MCE problems. |
| 20 |
|
| 21 |
Wrong. memtest86 giving you errors almost always indicates a hardware |
| 22 |
problem. You have changed the memory, but what remained consistent? The |
| 23 |
memory bus! Try a new system board. |
| 24 |
|
| 25 |
> I also tried something else that had an enormous positive effect on the |
| 26 |
> situation---I changed -march=pentium4 to -march=pentium3 in my CFLAGS |
| 27 |
|
| 28 |
All you have done is turn off SSE2 instructions and possibly a few |
| 29 |
others that the P4s have and the P3s do not. If something is wrong with |
| 30 |
your system board or CPU, less stress on the CPU is likely not to show |
| 31 |
problems as often. |
| 32 |
|
| 33 |
You have bad hardware, Kevin. Try the compile test with one CPU at a |
| 34 |
time (i.e. take one out), and if that is not illuminating, replace the |
| 35 |
system board. |
| 36 |
|
| 37 |
-- |
| 38 |
Josh Glover |
| 39 |
|
| 40 |
Gentoo Developer (http://dev.gentoo.org/~jmglov/) |
| 41 |
Tokyo Linux Users Group Listmaster (http://www.tlug.jp/) |
| 42 |
|
| 43 |
GPG keyID 0xDE8A3103 (C3E4 FA9E 1E07 BBDB 6D8B 07AB 2BF1 67A1 DE8A 3103) |
| 44 |
gpg --keyserver pgp.mit.edu --recv-keys DE8A3103 |
Archives