From: Soeren Sonnenburg <kernel@nn7.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Justin Mattock <justinmattock@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: suspend issue
Date: Fri, 11 Apr 2008 14:11:29 +0200 [thread overview]
Message-ID: <1207915890.4526.32.camel@localhost> (raw)
In-Reply-To: <20080411105712.GC18770@elf.ucw.cz>
On Fri, 2008-04-11 at 12:57 +0200, Pavel Machek wrote:
> On Fri 2008-04-11 00:05:52, Soeren Sonnenburg wrote:
[...]
> > > Well, 2.6.20 worked, so bisect should be easy, right?
> >
> > I don't quite understand... 2.6.24 worked yes, but 2.6.25-rc1 didn't
> > even *suspend*. However the problem lies not in suspending but no
> > display on *resume*. So the bug is hidden by the hang on suspend and I
> > don't see how I can check when resume broke.
>
> Hmm, you could bisect the resume regression, revert that, and then go
> on to find the suspend regression.
>
> ...ok, not easy, I see.
>
> Do you have kernel.org bugzilla # I could look at? Perhaps this can be
> debugged using printks or something...
http://bugzilla.kernel.org/show_bug.cgi?id=10319
Soeren
prev parent reply other threads:[~2008-04-11 12:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 4:03 suspend issue Justin Mattock
2008-04-06 13:55 ` Soeren Sonnenburg
2008-04-06 15:48 ` Justin Mattock
2008-04-06 20:31 ` Rafael J. Wysocki
2008-04-07 10:35 ` Rafael J. Wysocki
2008-04-06 23:28 ` Pavel Machek
2008-04-07 0:08 ` Justin Mattock
2008-04-07 8:41 ` R. J. Wysocki
2008-04-07 16:41 ` Justin Mattock
2008-04-09 10:25 ` Soeren Sonnenburg
2008-04-09 15:06 ` Justin Mattock
2008-04-10 10:02 ` Pavel Machek
2008-04-10 16:04 ` Justin Mattock
2008-04-10 22:05 ` Soeren Sonnenburg
2008-04-11 5:18 ` Justin Mattock
2008-04-11 5:32 ` Soeren Sonnenburg
2008-04-11 6:12 ` Justin Mattock
2008-04-11 10:57 ` Pavel Machek
2008-04-11 12:11 ` Soeren Sonnenburg [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=1207915890.4526.32.camel@localhost \
--to=kernel@nn7.de \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox