public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Len Brown <lenb@kernel.org>,
	akpm@linux-foundation.org, linux-acpi@vger.kernel.org,
	mingo@elte.hu, ak@suse.de
Subject: Re: [patch 02/13] ACPI, i686, x86_64: fix laptop bootup hang in init_acpi()
Date: Fri, 9 Feb 2007 17:13:50 -0200	[thread overview]
Message-ID: <20070209191350.GC4536@khazad-dum.debian.net> (raw)
In-Reply-To: <20070209180128.GA8586@srcf.ucam.org>

On Fri, 09 Feb 2007, Matthew Garrett wrote:
> On Fri, Feb 09, 2007 at 12:26:22PM -0200, Henrique de Moraes Holschuh wrote:
> > According to a patch sent to LKML a while ago that blacklisted all ThinkPads
> > from nmi_watchdog, the ThinkPad SMBIOS does INT 0x10 or something else that
> > will cause double or triple-faults if an NMI happens while in SMBIOS mode.
> 
> This is hardly unique to Thinkpads - huge arrays of things can trigger 
> SMM on pretty much any laptop. It's rarer on desktops, but some servers 
> have similar issues.

Well, that looks like a reason to blacklist it on thinkpads (and anything
else known to break on NMIs during SMM) and *ALSO* to add nmi_watchdog
guards around every call into the BIOS and ACPI tables, and every known
switch into SMM mode (i.e. anything using IBM's smapi, for example).  Yikes.

Not to mention that it should be documented, so that people get to know it
is potentially unsafe and don't turn it on without a reason.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

      reply	other threads:[~2007-02-09 19:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-06  0:09 [patch 02/13] ACPI, i686, x86_64: fix laptop bootup hang in init_acpi() akpm
2007-02-09  6:14 ` Len Brown
2007-02-09 14:26   ` Henrique de Moraes Holschuh
2007-02-09 18:01     ` Matthew Garrett
2007-02-09 19:13       ` Henrique de Moraes Holschuh [this message]

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=20070209191350.GC4536@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mjg59@srcf.ucam.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