From: "H. Peter Anvin" <hpa@zytor.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jeff Chua <jeff.chua.linux@gmail.com>,
"Antonino A. Daplas" <adaplas@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
suspend-devel List <suspend-devel@lists.sourceforge.net>
Subject: Re: Linux 2.6.23-rc2
Date: Mon, 06 Aug 2007 09:40:40 -0700 [thread overview]
Message-ID: <46B74F08.1050909@zytor.com> (raw)
In-Reply-To: <200708061326.25888.rjw@sisk.pl>
Rafael J. Wysocki wrote:
> On Monday, 6 August 2007 02:36, Jeff Chua wrote:
>> On 8/6/07, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>>
>>> What does 's2ram -i' say about your machine?
>> This machine can be identified by:
>> sys_vendor = "LENOVO"
>> sys_product = "1702E7A"
>> sys_version = "ThinkPad X60s"
>> bios_version = "7BETD0WW (2.11 )"
>
> This means it's not in the whitelist, AFAICS.
>
> Similar machines are known to work with "--acpi_sleep=3" or with
> "--acpi_sleep=1 --vbe_mode".
>
I'm not all that familiar with s2ram. Any feel for why the behaviour
would have changed from the old setup code at all? Since the setup code
isn't entered on resume from STR (unlike resume from STD), as far as I
know, there can only be "some little bit of state" hanging around.
If not then perhaps we should try to get a dump of the real-mode state
area for both kernels (which would need a patch, unfortunately.)
-hpa
next prev parent reply other threads:[~2007-08-06 16:41 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 12:11 Linux 2.6.23-rc2 Jeff Chua
2007-08-05 12:40 ` Antonino A. Daplas
2007-08-05 13:26 ` Jeff Chua
2007-08-05 16:47 ` Rafael J. Wysocki
2007-08-06 0:36 ` Jeff Chua
2007-08-06 11:26 ` Rafael J. Wysocki
2007-08-06 12:34 ` Jeff Chua
2007-08-06 16:40 ` H. Peter Anvin [this message]
2007-08-06 19:17 ` [Suspend-devel] " Rafael J. Wysocki
2007-08-06 15:40 ` Jan Engelhardt
2007-08-06 16:06 ` Jeff Chua
2007-08-06 16:34 ` Jan Engelhardt
2007-08-06 16:46 ` Indan Zupancic
2007-08-06 17:16 ` H. Peter Anvin
2007-08-06 17:32 ` Indan Zupancic
2007-08-06 17:33 ` H. Peter Anvin
2007-08-06 22:53 ` Jeff Chua
2007-08-06 22:54 ` H. Peter Anvin
2007-08-06 22:57 ` Jeff Chua
2007-08-06 23:00 ` H. Peter Anvin
2007-08-06 22:48 ` Jeff Chua
-- strict thread matches above, loose matches on Subject: below --
2007-08-06 23:20 Jeff Chua
2007-08-04 3:50 Linus Torvalds
2007-08-04 4:14 ` david
2007-08-04 5:13 ` Jeff Chua
2007-08-04 5:34 ` Jeff Chua
2007-08-04 13:52 ` Jeff Chua
2007-08-04 16:11 ` Linus Torvalds
2007-08-04 18:06 ` H. Peter Anvin
2007-08-04 21:02 ` Antonino A. Daplas
2007-08-05 2:37 ` Jeff Chua
2007-08-05 3:11 ` H. Peter Anvin
2007-08-05 11:52 ` Jeff Chua
2007-08-07 17:05 ` David Weinehall
2007-08-08 2:46 ` Jeff Chua
2007-08-05 2:29 ` Jeff Chua
2007-08-05 12:04 ` Jeff Chua
2007-08-04 10:30 ` Rafael J. Wysocki
2007-08-04 22:15 ` Rafael J. Wysocki
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=46B74F08.1050909@zytor.com \
--to=hpa@zytor.com \
--cc=adaplas@gmail.com \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=suspend-devel@lists.sourceforge.net \
--cc=torvalds@linux-foundation.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