From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Martin Michlmayr <tbm@cyrius.com>,
"elendil@planet.nl" <elendil@planet.nl>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
fengguang.wu@intel.com
Subject: Re: [2.6.28] Kernel panic after closing lid on HP 2510p
Date: Thu, 15 Jan 2009 02:59:45 +0000 [thread overview]
Message-ID: <20090115025945.GA19472@srcf.ucam.org> (raw)
In-Reply-To: <1231988103.20746.149.camel@rzhang-dt>
On Thu, Jan 15, 2009 at 10:55:03AM +0800, Zhang Rui wrote:
> DIDL is an IGD OpRegion field, as the Supported Display Devices ID List.
> it's evaluated by the _DOD method when ACPI video driver is loaded.
> And according to the spec, "The graphics driver writes to this field
> once during its initialization"
> if DIDL is not empty, a flag is set and the SMI will not be invoked when
> closing the lid.
> In our tests, this field (DIDL) is set in windows when _DOD is invoked
> while it's not in Linux.
> I can workaround this bug by setting the DIDL manually in AML code.
Oh, huh. Yeah, that sounds plausible. I'll give it a go here tomorrow.
--
Matthew Garrett | mjg59@srcf.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-01-15 2:59 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
2009-01-15 2:21 ` Matthew Garrett
2009-01-15 2:55 ` Zhang Rui
2009-01-15 2:59 ` Matthew Garrett [this message]
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=20090115025945.GA19472@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=akpm@linux-foundation.org \
--cc=elendil@planet.nl \
--cc=fengguang.wu@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
--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