| 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
| ||
|
Date: Tue, 26 Feb 2008 23:51:14 +0100 From: Pavel Machek <pavel@....cz> To: Dave Jones <davej@...emonkey.org.uk>, Andrew Morton <akpm@...ux-foundation.org>, "Rafael J. Wysocki" <rjw@...k.pl>, 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) On Tue 2008-02-26 17:23:37, Dave Jones 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. > > The actual whitelists still live in hal (or specifically hal-data), > rather than pm-utils. /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-* > for example. This gets passed down to pm-utils by hal. Well... you can keep the whitelist where you prefer it -- it may make sense for support of desktops... > > /usr/lib/pm-utils/functions > > > > ... > > > > if [ -x /usr/sbin/s2ram ]; then > > if [ -n "$S2RAM_OPTS" ]; then > > # Trust HAL or the user to pass the correct > > options > > /usr/sbin/s2ram $S2RAM_OPTS > > elif /usr/sbin/s2ram --test > /dev/null ; then > > # Trust s2ram's internal whitelist > > /usr/sbin/s2ram > > else > > # Unknown machine > > echo "This machine is unkown, please try to > > find out how to suspend this machine. See s2ram(8)." > > fi > > else > > echo -n "mem" > /sys/power/state > > fi > > Seems to be a debian specific change, the variant in Fedora, nor upstream > pm-utils doesn't have any of that. Possibly because it's a dumb idea > to have two separate sources of the same information. > > > ...so it is ready to use s2ram, but will fall back to > > echo. Unfortunately, that will mean no video resume on _many_ > > machines. > > > > To give some numbers: according to s2ram whitelist, we can restore > > video on 410 machines. On 74 of them, s2ram is not needed. So > > approximately 80% of machines need s2ram (at least in configuration > > without X running).... > > > > Pretty please, can we get s2ram for Fedora, so that video is restored > > there? > > I'm not the gatekeeper of what goes into Fedora userspace, but I'm pretty > certain the path forward has already been decided. Running a modern > Fedora desktop installation without hal just isn't feasible. Unfortunately, your decision means few things: 1) we can't debug it easily: I can no longer tell Andrew to boot into init=/bin/bash , and run s2ram. For debugging, trying with minimal system is very important. 2) you use bunch of shellscripts. If your SATA does not wake up, you get no video, and probably no chance to pull debug info out of that box. s2ram is pagelocked for that reason. ...plus, you could easily keep your whitelist in HAL and just call s2ram, unless user is running it manually. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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