Re: NMI watchdog question

>> On Mon, 2005-03-07 at 11:16 +0100, Mikael Pettersson wrote: >> Please try nmi_watchdog=2. > > tried, doesn't work.. much less NMI interrupts in /proc/interrupts this > time although, nmi_watchdog=1 works well when this crazy module loaded may it be a hardware bug? or maybe a usual thing t

Re: NMI watchdog question

On Mon, 2005-03-07 at 11:16 +0100, Mikael Pettersson wrote: > On Sun, 06 Mar 2005 01:53:25 +0100, Pallai Roland wrote: > > 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/dapro

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 s

Re: NMI watchdog question

Robert Hancock wrote: >> 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

Re: NMI watchdog question

Pallai Roland wrote: Hi, 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.. environment: P4C800 moth

NMI watchdog question

Hi, 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.. environment: P4C800 motherboard, P4-2.4 cpu