lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46B74F08.1050909@zytor.com>
Date:	Mon, 06 Aug 2007 09:40:40 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	Jeff Chua <jeff.chua.linux@...il.com>,
	"Antonino A. Daplas" <adaplas@...il.com>,
	lkml <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	suspend-devel List <suspend-devel@...ts.sourceforge.net>
Subject: Re: Linux 2.6.23-rc2

Rafael J. Wysocki wrote:
> On Monday, 6 August 2007 02:36, Jeff Chua wrote:
>> On 8/6/07, Rafael J. Wysocki <rjw@...k.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ