linux-kernel - Re: broken suspend in .2.6.25-rc3 on T61p (was Re: new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p)

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: <47C586F1.2030803@suse.de>
Date:	Wed, 27 Feb 2008 16:51:13 +0100
From:	Stefan Seyfried <seife@...e.de>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>, Pavel Machek <pavel@....cz>,
	Dave Jones <davej@...emonkey.org.uk>,
	Andrew Morton <akpm@...ux-foundation.org>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: broken suspend in .2.6.25-rc3 on T61p (was Re: new regression
 in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p)

Rafael J. Wysocki wrote:
> On Wednesday, 27 of February 2008, Matthew Garrett wrote:
>> On Tue, Feb 26, 2008 at 10:56:41PM +0100, Pavel Machek wrote:
>>
>>> Seems like pm-utils is just a thin wrapper around s2ram, at least in
>>> version debian ships. It does not seem to have its own whitelist.
>> That's a Debian patch.

Yes, the current openSUSE basically uses the same setup, but this will change
in the future.

>>> ...so it is ready to use s2ram, but will fall back to
>>> echo. Unfortunately, that will mean no video resume on _many_
>>> machines.
>> See /usr/lib/pm-utils/sleep.d/99video .
>>
>>> Pretty please, can we get s2ram for Fedora, so that video is restored
>>> there?
>> Stefan told us at FOSDEM that s2ram was being deprecated in OpenSuse, so 
>> I don't think this is the way to go.
> 
> Well, is that really correct?  Stefan??

Not quite :-)

> He probably meant that the s2ram _whitelist_ is going to be deprecated, which
> didn't mean s2ram altogether.

Exactly.

> s2ram is pretty useful anyway, as it combines many mechanisms that allow us to
> bring the video back to life from the user land, so you can use one binary
> instead of a bunch of different programs with different command lines etc.

That's what i like about it and the part i want to keep: do all the
workarounds in one place, ideally with locked VTs and maybe mlock()ed, but get
the workaround options from HAL.

I also had the impression that i had said this quite clearly, but the talk was
short, so the "data compression" of the information might not have been
lossless :-)

Hope this helps to clear up the confusion.
-- 
Stefan Seyfried
R&D Team Mobile Devices            |              "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."

This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
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/