From: Andrew Watts <akwatts@ymail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-pm@lists.linux-foundation.org, tj@kernel.org,
dmitry.torokhov@gmail.com
Subject: [REGRESSION]: hibernate/sleep regression w/ bisection
Date: Tue, 1 Nov 2011 07:48:19 -0500 [thread overview]
Message-ID: <20111101124759.GA1326@zeus> (raw)
Hi.
Hibernate/sleep (echo disk/mem > /sys/power/state) has presented problems
for me starting with 2.6.39. Kernel 2.6.37.6 was the last completely bug-free
version I used (I skipped the 2.6.38 branch entirely).
The symptoms are that upon resume (from sleep/hibernate) there is no video
nor any keyboard input with the exception of sysrq.
It has been a frustrating bug to hunt down because it is not easily
reproduced; sometimes the bug doesn't pop up until after a long sequence of
hibernate/sleep cycles.
I successfully bisected the problem to: 8ee294cd9def000.
=======
Commit: 8ee294cd9def0004887da7f44b80563493b0a097
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date: Mon Nov 15 01:39:57 2010 -0800
Input: serio - convert to common workqueue instead of a thread
=======
Backing out 8ee294cd9def000 (which requires reversing part of
1d64b655dc083df also) fixes this particular problem on 2.6.39.4,
3.0.8, and 3.1.
Unfortunately, in 3.0.8 and 3.1 I have other suspend/hibernate problems
that I will investigate next and detail in a different regression report.
~ Andy
System specs: P4/Radeon GPU
next reply other threads:[~2011-11-01 12:48 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 12:48 Andrew Watts [this message]
2011-11-01 16:42 ` [REGRESSION]: hibernate/sleep regression w/ bisection Tejun Heo
2011-11-01 16:42 ` Tejun Heo
2011-11-01 19:15 ` Andrew Watts
2011-11-01 20:19 ` Tejun Heo
2011-11-01 20:19 ` Tejun Heo
2011-11-02 0:24 ` Andrew Watts
2011-11-02 0:24 ` Andrew Watts
2011-11-01 19:15 ` Andrew Watts
2011-11-02 5:46 ` Dmitry Torokhov
2011-11-02 5:46 ` Dmitry Torokhov
2011-11-02 15:04 ` Andrew Watts
2011-11-02 15:04 ` Andrew Watts
2011-11-02 16:02 ` Andrew Watts
2011-11-02 16:02 ` Andrew Watts
2011-11-02 16:31 ` Dmitry Torokhov
2011-11-02 16:31 ` Dmitry Torokhov
2011-11-02 17:01 ` Andrew Watts
2011-11-02 17:08 ` Dmitry Torokhov
2011-11-02 17:08 ` Dmitry Torokhov
2011-11-02 17:01 ` Andrew Watts
2011-11-03 15:59 ` Tejun Heo
2011-11-03 15:59 ` Tejun Heo
2011-11-03 18:46 ` Andrew Watts
2011-11-03 18:46 ` Andrew Watts
2011-11-03 21:39 ` Tejun Heo
2011-11-03 21:39 ` Tejun Heo
2011-11-04 13:44 ` Andrew Watts
2011-11-04 16:14 ` Tejun Heo
2011-11-04 16:48 ` Jerome Glisse
2011-11-04 16:48 ` Jerome Glisse
2011-11-04 17:34 ` Andrew Watts
2011-11-04 17:35 ` Jerome Glisse
2011-11-04 23:08 ` Andrew Watts
2011-11-04 23:08 ` Andrew Watts
2011-11-21 21:09 ` Tejun Heo
2011-11-21 21:09 ` Tejun Heo
2011-11-21 21:29 ` Jerome Glisse
2011-11-22 11:40 ` Andrew Watts
2011-11-22 11:40 ` Andrew Watts
2011-11-21 21:29 ` Jerome Glisse
2011-11-04 17:35 ` Jerome Glisse
2011-11-04 17:44 ` Jerome Glisse
2011-11-04 17:44 ` Jerome Glisse
2011-11-04 18:45 ` Andrew Watts
2011-11-04 18:45 ` Andrew Watts
2011-11-04 17:34 ` Andrew Watts
2012-04-25 20:04 ` Andrew Watts
2011-11-04 16:14 ` Tejun Heo
2011-11-04 13:44 ` Andrew Watts
-- strict thread matches above, loose matches on Subject: below --
2011-11-01 12:48 Andrew Watts
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=20111101124759.GA1326@zeus \
--to=akwatts@ymail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=tj@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.