public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Martin Michlmayr <tbm@cyrius.com>,
	elendil@planet.nl, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org
Subject: Re: [2.6.28] Kernel panic after closing lid on HP 2510p
Date: Wed, 14 Jan 2009 18:15:42 -0800	[thread overview]
Message-ID: <20090114181542.34614acf.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090115020311.GA18740@srcf.ucam.org>

On Thu, 15 Jan 2009 02:03:11 +0000 Matthew Garrett <mjg59@srcf.ucam.org> wrote:

> On Wed, Jan 14, 2009 at 04:26:03PM -0800, Andrew Morton wrote:
> 
> > It'd be a very special BIOS bug if it can reach out and make the kernel
> > oops.
> 
> Lid actions typically trigger SMI code, so it's entirely capable of 
> destroying CPU state in such a way that the kernel falls over (and 
> probably even in ways that cause the kernel to turn green, emit pleasing 
> warbling noises or invade neighbouring pieces of hardware). In this case 
> it seems to be SMP specific - the system's entirely stable in UP mode. 
> It's greatly vexing.

Does it always crash in the same way?

If so, we can put crash-avoidance code at the offending callsite and
back out gracefully?


  reply	other threads:[~2009-01-15  2:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200901121356.46236.elendil@planet.nl>
     [not found] ` <20090113123056.GA2464@deprecation.cyrius.com>
2009-01-15  0:26   ` [2.6.28] Kernel panic after closing lid on HP 2510p Andrew Morton
2009-01-15  2:03     ` Matthew Garrett
2009-01-15  2:15       ` Andrew Morton [this message]
2009-01-15  2:21         ` Matthew Garrett
2009-01-15  2:55           ` Zhang Rui
2009-01-15  2:59             ` Matthew Garrett
2009-01-15  4:20             ` Wu Fengguang
2009-01-15  7:41             ` Martin Michlmayr

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=20090114181542.34614acf.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=elendil@planet.nl \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=tbm@cyrius.com \
    /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