public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: NMI watchdog question
Date: Sun, 06 Mar 2005 09:14:33 -0600	[thread overview]
Message-ID: <422B1E59.4060009@shaw.ca> (raw)
In-Reply-To: <3EShS-A1-9@gated-at.bofh.it>

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 motherboard, P4-2.4 cpu (APIC 2.0 on)
>  Promise 20378 SATA controller on the motherboard (sil_promise driver)
>  Maxtor diamondmax plus 9 200G sata disk
>  (and an empty PCI expander plus some more other under-testing hardware
> which doesn't matter in the experiment)
> 
>  mainline kernel 2.6.11
>  serial and VGA console, root on NFS
> 
> 
> 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 :(

The NMI watchdog only triggers if something is blocking interrupts from 
getting through - if timer interrupts are still happening it won't 
activate. You can try Alt-Sysrq-T to get a traceback of where the 
current process is stuck..

       reply	other threads:[~2005-03-06 15:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3EShS-A1-9@gated-at.bofh.it>
2005-03-06 15:14 ` Robert Hancock [this message]
2005-03-08  2:28 NMI watchdog question Pallai Roland
  -- strict thread matches above, loose matches on Subject: below --
2005-03-07 10:16 Mikael Pettersson
2005-03-07 13:00 ` Pallai Roland
2005-03-06 18:51 Pallai Roland
2005-03-06  0:53 Pallai Roland
2002-11-06  5:50 george anzinger
2002-11-06 10:53 ` Mikael Pettersson
2002-11-06 17:59   ` george anzinger
2002-11-06 18:12     ` John Levon
2002-11-06 18:58       ` Maciej W. Rozycki
2002-11-06 18:55     ` Maciej W. Rozycki
2002-11-06 19:49       ` george anzinger
2002-11-06 20:07         ` John Levon
2002-11-07 16:20           ` Bill Davidsen
2002-11-07 16:30             ` Maciej W. Rozycki
2002-11-07 16:44             ` Zwane Mwaikambo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=422B1E59.4060009@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox