I have 2.0.34 and 2.0.35 with SMP 1.1 and 1.4 BIOSes without any problem.
Sure this is not _the_ reason to go 2.1.xxx.
> When I compiled and installed the new kernel the machine reboots and sees
> both processors (yay!) and starts working normally. After about 17 to 19
> minutes though it completely locks and reboots. It's a hard enough reboot
> that the machines built in error light comes on which is only supposed to
> happen in case of hardware failure. The machine will cycle and through and
> continue this process every 17 to 19 minutes. The first thing I tried was
> pulling the second processor and making it run on just one. It didn't change
> anything.
I saw a similar problem in one of our machines when the total memory was
specified in lilo.conf (is this your case?), although the live cycle was a
couple of hours (it depends on available ram and workload). Specifying
(1) MB less in lilo.conf solved the problem (related to bios shadowing, some
bioses can not be changed not to shadow).
If you are going to use SMP and 2.0.xx (I found 2.0.35 is really bad for
SMP,
2.0.33 and 2.0.34 performs a little better/longer), I strongly recommend you
2.0.36 (is en pre19 at the moment but it is rock solid in my machine). It
is a big step from 2.0.35, recognizes all available ram also has _much_
better adaptec drivers.
Good luck.
--ricardo
PS: Did anyone see the report of the contract between TurboLinux and Adaptec
to develop "better Adaptec" drivers for Linux? What does it mean? Are they
going to improve Doug drivers or start from scracht?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/