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: <1212343465.3373.60.camel@localhost.localdomain>
Date:	Sun, 01 Jun 2008 13:04:25 -0500
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Pavel Machek <pavel@....cz>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	David Miller <davem@...emloft.net>, tytso@....edu,
	benh@...nel.crashing.org,
	ksummit-2008-discuss@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org, seife@...e.de
Subject: Re: s2ram video problems Re: [Ksummit-2008-discuss] Fixing the
	Kernel Janitors project

On Sun, 2008-06-01 at 18:21 +0200, Pavel Machek wrote:
> Hi!
> 
> > > Fix NOHZ/CPUIDLE along with suspend/resume on all participants
> > > laptops, which are probably 50+ different models. That'd be an odd
> > > enough mix of wreckaged hardware / BIOS / ACPI.
> > > 
> > > Should be fun and solve a bunch of hard to grok bugs in the bugzillas
> > > along the way.
> > 
> > Well ... in theory.
> > 
> > In practice, for instance, my laptop had suspend/resume working shortly
> > after I got it, and the widescreen video too.  Most of the problems were
> > video related, so I did interact with the upstream intel video driver
> > people, but by and large it was a set of black magic rules to restore
> > the video to its prior state (in my case, even the vbe tools didn't work
> > and I had to manually save and restore the pci config space).
> 
> that's s2ram -v, right? Can you submit a whitelist entry so it starts
> working for other people, too?

Actually, it's pm-utils, because I'm using fedora.

This, by the way was years ago, beginning with FC6.  In FC7 we got the
driver to the state where vbestate save/restore worked for it and added
it to the hal database.  Today, at FC9, I've just been busy filing a bug
with fedora because the i915 drm now seems to do everything and actively
screws up if vbestate save/restore is used (so all the work I did with
FC7/8 now needs to be undone).

James


--
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