> This bug is definitely due to the changes in device locking. The machine
> doesn't actually really die, and the system works fine _except_ that all
> IO to a certain controller will block forever (which, when the disk is
> your main filesystem, will obviously appear as a complete lockup).
>
> You can see it by noticing that the machine still answers to the network,
> and running programs will actually continue to run (unless they need to do
> any IO), but yes, the machine is pretty dead. At least that's the symptoms
> I see.
I just got a hard lockup in 2.1.94 under minimal load (just X) which froze
mouse, network, keyboard, etc... Nothing unusual going on at the time...
Only happened once so far.
dual ppro 150 with:
Module Size Used by
ne 5700 1
8390 5824 0 [ne]
joystick 9280 0 (unused)
nfs 31884 0 (unused)
lockd 27568 0 [nfs]
sunrpc 48892 0 [nfs lockd]
ide-cd 20232 0
cdrom 9448 0 [ide-cd]
mad16 4812 1
uart401 5508 1 [mad16]
ad1848 14128 1 [mad16]
sound 56860 0 [mad16 uart401 ad1848]
psaux 2356 1
misc 676 1 [psaux]
msdos 6864 1
fat 23876 1 [msdos]
binfmt_aout 3812 1
ewrk3 12733 1
-bevan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu