Messages in this thread | | | Date | Mon, 7 Mar 2005 11:16:49 +0100 (MET) | From | Mikael Pettersson <> | Subject | Re: NMI watchdog question |
| |
On Sun, 06 Mar 2005 01:53:25 +0100, Pallai Roland wrote: > I'm playing with the NMI watchdog (nmi_watchdog=1) on a reproductable >hard lockup (no keyboard, etc) but seems like it doesn't works and I >can't understand why, please explain to me the possible causes.. I >belive it should work in this situation.. ... >steps to the lockup: > 1. booting the machine with sata drive on the promise controller > 2. dd if=/dev/sda of=/dev/null bs=4k > 3. unplug the power from drive > 4. waiting about 2 seconds > 5. plug the power back > > dd stucked in 'D' here for 10-15 seconds and than the kernel say: > ata1: command timeout > > and voila, the box is dead, but without any message from the NMI >watchdog :( ... >Kernel command line: auto BOOT_IMAGE=l2611-1S0 ro nfsroot=192.168.4.254:/mnt/daproot,v3 ip=192. >168.4.5::192.168.4.254:255.255.255.0::eth0:none console=tty0 console=ttyS0,115200 nmi_watchdog= >1 3
Please try nmi_watchdog=2. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |