Over the last week I've tried to upgrade a 4-CPU Xeon box to 2.2.19, but
the it keeps locking up whenever the disks are stresses a bit, e.g. when
updatedb is running. I get the following messages on the console:
wait_on_bh, CPU 1:
irq: 1 [1 0]
bh: 1 [1 0]
over and over again, until somebody pushes the reset button. 8010af71 is
somewhere in the middle of synchronize_bh().
The hardware configuration is: 4 Xeon/500MHz, 1GB RAM, 3 SCSI disks
attached to a symbios controller, 2 eepro100 interfaces. The kernel is
compiled with support for SMP and 2GB of RAM (hence the kernel address
starting with 8 instead of c). It was compiled from a pristine source
tree, no patches were applied.
I had more problems with 2.2.19 and another SMP box, which was also
locking up under stress. I'm not sure if it had the same messages on the
console, since it's headless, but it was running the same 2.2.19 kernel as
the previous one and was locking up in a very similar fashion. The
hardware in that box is 2 P-III/750MHz, 512MB RAM, 1 IDE disk on a PIIX
controller, and an unused aic7xxx SCSI controller with no SCSI devices
attached to it.
Both boxes are rock-solid when running 2.2.18-SMP.
Any ideas? Has anybody else reported this with 2.2.19?
-- It is better to keep your mouth shut and be thought a fool, than to open it and remove all doubt.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Apr 30 2001 - 21:00:21 EST