From: Zhang Rui <rui.zhang@intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: ACPI crash on lid close - SMP race?
Date: Tue, 11 Nov 2008 09:27:14 +0800 [thread overview]
Message-ID: <1226366834.15014.60.camel@rzhang-dt> (raw)
In-Reply-To: <20081110161105.GA2041@srcf.ucam.org>
well, there is a bug report for this problem:
http://bugzilla.kernel.org/show_bug.cgi?id=11259
and there are some bug reports for a similar problem (system crashes on
lid close if _DOS=1, but on a UP platform).
http://bugzilla.kernel.org/show_bug.cgi?id=6001#c49
but unfortunately we haven't made any progress in this issue. :(
thanks,
rui
On Tue, 2008-11-11 at 00:11 +0800, Matthew Garrett wrote:
> If the _DOS flag on my HP 2510p is set to 0 (ie, signal OS when screen
> notification is requested, don't change automatically) then it'll crash
> on random lid open/closes. The trace generally makes little sense and
> depends on the kernel version and phase of the moon. I'd ignored this as
> firmware brokenness up until lately, but since having _DOS set to 0 is
> the only way to get a notification when the display switch key is
> pressed on this machine I'd be interested in fixing it properly.
>
> Unfortunately, I've got no real idea what on earth is going on. The only
> clue I've found so far is that booting with maxcpus=1 leaves it working
> perfectly. What parts of the ACPI stack could be triggering this?
>
next prev parent reply other threads:[~2008-11-11 1:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 16:11 ACPI crash on lid close - SMP race? Matthew Garrett
2008-11-10 17:26 ` Sergio Monteiro Basto
2008-11-10 17:29 ` Matthew Garrett
2008-11-10 23:52 ` Sergio Monteiro Basto
2008-11-11 1:27 ` Zhang Rui [this message]
2008-11-11 1:33 ` Matthew Garrett
2008-11-11 1:59 ` Zhang Rui
2008-11-11 2:05 ` Matthew Garrett
2008-11-12 5:21 ` Sergio Monteiro Basto
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=1226366834.15014.60.camel@rzhang-dt \
--to=rui.zhang@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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