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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <900814656-1239422746-cardhu_decombobulator_blackberry.rim.net-2124207137-@bxe1152.bisx.prod.on.blackberry>
Date:	Sat, 11 Apr 2009 04:04:51 +0000
From:	"Theodore Tso" <tytso@....edu>
To:	"Jeff Chua" <jeff.chua.linux@...il.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	"Pavel Machek" <pavel@....cz>, linux-kernel@...r.kernel.org
Subject: Re: suspend-to-ram broken on X61 thinkpads in 2.6.30-rc1?

So I tried to do a bisect using a reduced config, and I wasn't able to reproduce.  So I went back to 2.6.30-rc1 and started playing with configurations.   I was able to finally get a reproduction, and I found that the af_packet module seems to be responsible.   If I move the modules directory out of the way and reboot, then manually insmod the af_packet module, then suspend, it fails by hanging with the flashing moon LED.  If I reboot and don't load the af_packet module, the suspend works.   Needless to say this falls into the WTF category.   I will do more testing to see what's up...

     - Ted

-----Original Message-----
From: Jeff Chua <jeff.chua.linux@...il.com>

Date: Sat, 11 Apr 2009 09:12:28 
To: Rafael J. Wysocki<rjw@...k.pl>
Cc: Pavel Machek<pavel@....cz>; Theodore Ts'o<tytso@....edu>; <linux-kernel@...r.kernel.org>
Subject: Re: suspend-to-ram broken on X61 thinkpads in 2.6.30-rc1?

On Sat, Apr 11, 2009 at 2:08 AM, Rafael J. Wysocki <rjw@...k.pl> wrote:

> Can you attach yours, so that we could compare, please?

Attached is my .config.

> I meant please test the kernel where commit
> 0a0c5168df270a50e3518e4f12bddb31f8f5f38f is the head.  It is possible
> that one of the commits immediately following it broke things.  If that's
> the case, this kernel will work for you.

I'll do that now.

Thanks,
Jeff.