[lkml]   [2001]   [Apr]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject2.4.x SMP issues on 440LX (?)

As another person (Aaron M. Folmsbee, 28.04.01-22:32) in here reported earlier, there seems to be problems
with Intel 440LX chipsets with dual CPU's and the Linux 2.4 kernel series.
Simply stated, this just plain doesn't work right. When sticking in only one CPU, the system boots fine, but I
see "random" hangs and kernel panics. Watching boot messages and doing a cat /proc/cpuinfo gives the
correct information; I have one Intel Pentium II installed.
However, when sticking in both CPU's, one of two things happen:
1 - The system doesn't boot at all. It either reboots straight after unpacking the kernel and doing the first CPU
initializations (can't see when, it's too fast), or it continues with the boot and kernel panics somewhere along
the way. Example kernel panic output is at the end of this mail. Wether it just reboots or hangs later depends
on which CPU is installed as CPU1, the two CPU's are both PII's but one is produced in the Phillipines, the
other in Malaysia.
2 - If I get another CPU produced in the Phillipines, less than 100 serial numbers apart, it boots and lets me log
in, and _seems_ stable. That is, until I put some load on it. After a few minutes or so it hangs again, or kernel
panics. Sometimes it gives me a panic message, sometimes not. But it seems to be the same message..

Now the _really_ interesting thing is - and this happens with 2.2 kernels aswell - when having both CPU's
installed, no matter which ones and where they are produced, it seemingly thinks one of them is a Celeron,
not a PII. It's always the second CPU, and cat /proc/cpuinfo and the bootmessages are consistent here. The
first CPU show up correctly as a PII with 256kb cache, the second shows up as a Celeron with 32kb cache..
Otherwise the CPU information is 100% equal (which it shouldn't be if it was indeed a celeron, right?).
Somehow I suspect that the reason for this "misinformation" might also be the reason for the instability.. But
IANAKH (i am not a kernel hacker), so I wouldn't know.

Hope someone does, though...

Best regards,
Eirik Overby

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.083 / U:0.304 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site