From: Robert Love <rml@tech9.net>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
reality@delusion.de, linux-kernel@vger.kernel.org
Subject: RE: [OOPS] Kernel powerdown
Date: 15 Mar 2002 16:40:41 -0500 [thread overview]
Message-ID: <1016228442.904.55.camel@phantasy> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C02AB7D01@orsmsx111.jf.intel.com>
In-Reply-To: <59885C5E3098D511AD690002A5072D3C02AB7D01@orsmsx111.jf.intel.com>
On Fri, 2002-03-15 at 16:30, Grover, Andrew wrote:
> Theoretically we should be turning the machine off, after which I'm pretty
> sure the NMI watchdog shouldn't be an issue :) but IIRC we are masking
> interrupts and doing some delays before turning off, so the NMI watchdog
> might not be liking that? APM doesn't turn off the NMI afaik so why should
> ACPI have to?
Hm, is the period with interrupts off during shutdown much greater with
ACPI than with APM? Maybe it is just simply that ...
You could sprinkle calls to
touch_nmi_watchdog()
in the ACPI shutdown code and see if the problem goes away ...
I am also curious about Andrew's question - does the system properly
shutdown without nmi-watchdog? The case could be that interrupts are
disabled and ACPI then goes to shut the system down, fails, and the
system just sits (like, say, a Windows 9x machine :>) and finally the
watchdog causes an OOPS. This seems most likely, in fact.
Robert Love
next prev parent reply other threads:[~2002-03-15 21:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 21:30 [OOPS] Kernel powerdown Grover, Andrew
2002-03-15 21:40 ` Robert Love [this message]
2002-03-15 21:44 ` Udo A. Steinberg
2002-03-15 21:55 ` Robert Love
2002-03-16 13:37 ` Tony Hoyle
2002-03-15 21:48 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-03-15 21:49 Grover, Andrew
2002-03-15 22:18 ` Udo A. Steinberg
2002-03-15 22:26 ` Robert Love
2002-03-15 22:40 ` Udo A. Steinberg
2002-03-15 21:17 Udo A. Steinberg
2002-03-15 21:30 ` Robert Love
2002-03-15 21:40 ` Alan Cox
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=1016228442.904.55.camel@phantasy \
--to=rml@tech9.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reality@delusion.de \
/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