From: Matt Mackall <mpm@selenic.com>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: 2.6.21rc suspend to ram regression on Lenovo X60
Date: Tue, 13 Mar 2007 09:41:36 -0500 [thread overview]
Message-ID: <20070313144136.GF10459@waste.org> (raw)
In-Reply-To: <20070313040828.GA17893@redhat.com>
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.
prev parent reply other threads:[~2007-03-13 14:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 4:08 2.6.21rc suspend to ram regression on Lenovo X60 Dave Jones
2007-03-13 8:11 ` Eric W. Biederman
2007-03-16 16:21 ` Pavel Machek
2007-03-16 18:37 ` Kok, Auke
2007-03-13 9:22 ` Rafael J. Wysocki
2007-03-13 13:22 ` Dave Jones
2007-03-15 16:11 ` Eric W. Biederman
2007-03-15 17:00 ` Dave Jones
2007-03-15 18:10 ` Dave Jones
2007-03-15 18:24 ` Eric W. Biederman
2007-03-15 19:45 ` Jeremy Fitzhardinge
2007-03-15 20:00 ` Dave Jones
2007-03-13 14:41 ` Matt Mackall [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070313144136.GF10459@waste.org \
--to=mpm@selenic.com \
--cc=davej@redhat.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.