linux-kernel - Re: suspend-to-ram broken on X61 thinkpads in 2.6.30-rc1?

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: <20090410164808.GA8491@mit.edu>
Date:	Fri, 10 Apr 2009 12:48:08 -0400
From:	Theodore Tso <tytso@....edu>
To:	Jeff Chua <jeff.chua.linux@...il.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>, linux-kernel@...r.kernel.org
Subject: Re: suspend-to-ram broken on X61 thinkpads in 2.6.30-rc1?

On Fri, Apr 10, 2009 at 09:00:08PM +0800, Jeff Chua wrote:
> 2009/4/10 Rafael J. Wysocki <rjw@...k.pl>:
> > On Friday 10 April 2009, Theodore Ts'o wrote:
> >> Hi, has anyone else noticed that suspend-to-ram seems to have gotten
> >> broken in 2.6.30-rc1, sometime during last half of the merge window?
> 
> My X61 STR is broken as well.
> 
> This commit is in the latest git, but it's does not seem to fix the
> problem. 2.6.29 STR works very well. And all the Think "Fn" keys are
> no longer working (LID close still functioning though ... but that
> could a configuration issue moving from 2.6.29 to 2.6.30-rc1.

I'm seeing this problem as well.

> Shall I do the bisecting? I think this is the only one not working for
> me other than the slow iptables that I reported earlier.

Well, I can save you at least one or two reboots, based on some
test kernels I had been building.

git bisect bad v2.6.30-rc1-git2
git bisect bad v2.6.30-rc1	
git bisect bad e0724bf6		(v2.6.29-git14 circa April 6th)
git bisect good 5d80f8e5	(v2.6.29-git3 circa March 27th)

Only 3,074 revisions to go.  :-)

          					- Ted


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