From: "Yu, Luming" <luming.yu@intel.com>
To: "Sanjoy Mahajan" <sanjoy@mrao.cam.ac.uk>
Cc: <linux-kernel@vger.kernel.org>,
"Linus Torvalds" <torvalds@osdl.org>,
"Andrew Morton" <akpm@osdl.org>,
"Tom Seeley" <redhat@tomseeley.co.uk>,
"Dave Jones" <davej@redhat.com>,
"Jiri Slaby" <jirislaby@gmail.com>, <michael@mihu.de>,
<mchehab@infradead.org>, <v4l-dvb-maintainer@linuxtv.org>,
<video4linux-list@redhat.com>,
"Brian Marete" <bgmarete@gmail.com>,
"Ryan Phillips" <rphillips@gentoo.org>, <gregkh@suse.de>,
<linux-usb-devel@lists.sourceforge.net>,
"Brown, Len" <len.brown@intel.com>, <linux-acpi@vger.kernel.org>,
"Mark Lord" <lkml@rtr.ca>, "Randy Dunlap" <rdunlap@xenotime.net>,
<jgarzik@pobox.com>, <linux-ide@vger.kernel.org>,
"Duncan" <1i5t5.duncan@cox.net>,
"Pavlik Vojtech" <vojtech@suse.cz>,
<linux-input@atrey.karlin.mff.cuni.cz>,
"Meelis Roos" <mroos@linux.ee>
Subject: RE: 2.6.16-rc5: known regressions
Date: Fri, 3 Mar 2006 12:46:06 +0800 [thread overview]
Message-ID: <3ACA40606221794F80A5670F0AF15F840B172CC2@pdsmsx403> (raw)
>
>>> Subject : S3 sleep hangs the second time - 600X
>>> References : http://bugzilla.kernel.org/show_bug.cgi?id=5989
>
>From: "Yu, Luming" <luming.yu@intel.com>
>> According to bug report, the BIOS DSDT is modified. I don't know
>> how these changes affect the results of suspend/resume. But, it is
>> clear this is NOT right approach to fix problem. Hence, I need the
>> testing report with un-modified DSDT on TP 600X, bios 1.11.
>
>I'll try it, although I don't think I'll get any data on the problem.
>The unmodified DSDT (bios 1.11) lacks an S3 sleep object, so I had to
>modify the DSDT even to get S3 to sleep at all. See
><http://bugzilla.kernel.org/show_bug.cgi?id=3534> for that discussion.
>In additional comment #4 there (2004-10-14), you said:
>
> The root cause of [the missing S3 object] failure is that linux is
> using element in
>
> const char *acpi_gbl_sleep_state_names[ACPI_S_STATE_COUNT] =
> {
> "\_S0_",
> "\_S1_",
> "\_S2_",
> "\_S3_",
> "\_S4_",
> "\_S5_"
> };
>
> to call acpi_get_sleep_type_data, but your box define _S3 under the
> device PNP0A03. So, the evaluating \_S3 will fail.
>
> The workaround in DSDT is to change _S3 to \_S3_ .
> We can fix it in acpi driver soon.
Hmm, this conclusion seems to be wrong. at that time, I said it too
early. The real problem is this, if your box support S3, the _S3 method
should return from ELSE-statement which return package
{0x01,0x01,0x00,0x00}.
If you still use this
http://bugzilla.kernel.org/show_bug.cgi?id=3534#c10 to
override your DSDT, which bypass the testing and blindly assume BIOS or
platform
do support S3, then I suggest you to retest, and post dmesg with
UN-modified BIOS.
Thanks,
Luming
Method (_S3, 0, NotSerialized)
{
If (BXPT)
{
Return (Package (0x04)
{
0x06,
0x06,
0x00,
0x00
})
}
Else
{
Return (Package (0x04)
{
0x01,
0x01,
0x00,
0x00
})
}
}
next reply other threads:[~2006-03-03 4:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 4:46 Yu, Luming [this message]
2006-03-03 5:58 ` 2.6.16-rc5: known regressions [600X S3 sleep] Sanjoy Mahajan
-- strict thread matches above, loose matches on Subject: below --
2006-02-27 9:04 2.6.16-rc5: known regressions Yu, Luming
2006-03-03 2:59 ` Sanjoy Mahajan
2006-03-03 16:51 ` Matthew Garrett
2006-03-03 21:04 ` Sanjoy Mahajan
2006-02-27 5:27 Linux v2.6.16-rc5 Linus Torvalds
2006-02-27 6:13 ` 2.6.16-rc5: known regressions Adrian Bunk
2006-02-27 6:26 ` Ryan Phillips
2006-02-27 6:39 ` Vojtech Pavlik
2006-02-27 6:54 ` Jeff Garzik
2006-02-27 7:08 ` Adrian Bunk
2006-02-28 9:40 ` Jens Axboe
2006-03-01 0:17 ` Randy.Dunlap
2006-03-04 13:18 ` Adrian Bunk
2006-02-27 13:36 ` Mark Lord
2006-02-27 14:09 ` Pavel Machek
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=3ACA40606221794F80A5670F0AF15F840B172CC2@pdsmsx403 \
--to=luming.yu@intel.com \
--cc=1i5t5.duncan@cox.net \
--cc=akpm@osdl.org \
--cc=bgmarete@gmail.com \
--cc=davej@redhat.com \
--cc=gregkh@suse.de \
--cc=jgarzik@pobox.com \
--cc=jirislaby@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=lkml@rtr.ca \
--cc=mchehab@infradead.org \
--cc=michael@mihu.de \
--cc=mroos@linux.ee \
--cc=rdunlap@xenotime.net \
--cc=redhat@tomseeley.co.uk \
--cc=rphillips@gentoo.org \
--cc=sanjoy@mrao.cam.ac.uk \
--cc=torvalds@osdl.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=video4linux-list@redhat.com \
--cc=vojtech@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).