linux-kernel - Re: 2.6.21rc suspend to ram regression on Lenovo X60

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: <20070313144136.GF10459@waste.org>
Date:	Tue, 13 Mar 2007 09:41:36 -0500
From:	Matt Mackall <mpm@...enic.com>
To:	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: 2.6.21rc suspend to ram regression on Lenovo X60

On Tue, Mar 13, 2007 at 12:08:28AM -0400, Dave Jones wrote:
> I spent considerable time over the last day or so bisecting to
> find out why an X60 stopped resuming somewhen between 2.6.20 and current -git.
> (Total lockup, black screen of death).
> 
> The bisect log looked like this.
> 
...
> Any ideas how to further debug this?
> I'll try backing out individual changes from that merge tomorrow.

If you've got a tree that looks like:

 --a-b-c-d-e-f-g-h->
    \           /
     i-j-k-l-m-n

where h is bad but both g and n are good, you can try testing the
merge of g+k, etc. Which will find half the problem. Then you can do
the same on the other side. Tedious.

The best way to debug resume issues directly seems to be to do a fake
suspend, possibly with filtering out particular devices:

http://lwn.net/Articles/219033/
http://www.uwsg.iu.edu/hypermail/linux/kernel/0701.3/0397.html

-- 
Mathematics is the supreme nostalgia of our time.
-
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/