From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 66751] New: Does not resume from suspend (bisected)
Date: Sat, 07 Dec 2013 12:30:38 +0000 [thread overview]
Message-ID: <bug-66751-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=66751
Bug ID: 66751
Summary: Does not resume from suspend (bisected)
Product: Power Management
Version: 2.5
Kernel Version: v3.13-rc3
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: cpufreq
Assignee: cpufreq@vger.kernel.org
Reporter: ziegler@uni-freiburg.de
Regression: No
Created attachment 117791
--> https://bugzilla.kernel.org/attachment.cgi?id=117791&action=edit
config for 3.13-rc3
This is on a Thinkpad T510. If a try to wake up the machine from suspend,
only the start button light changes from "blink" to "on". The screen remains
black and the machine is unresponsive. All I can do is a hard reboot by holding
down the start button.
I bisected between v3.13-rc2 and v3.13-rc3 and got
commit 2167e2399dc5e69c62db56d933e9c8cbe107620a
Author: Bj√∏rn Mork <bjorn@mork.no>
Date: Tue Dec 3 12:14:32 2013 +0100
cpufreq: fix garbage kobjects on errors during suspend/resume
as the first bad commit
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2013-12-07 12:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-07 12:30 bugzilla-daemon [this message]
2013-12-07 13:50 ` [Bug 66751] Does not resume from suspend (bisected) bugzilla-daemon
2013-12-07 21:19 ` bugzilla-daemon
2013-12-09 13:41 ` [Bug 66751] [BISECTED]Does " bugzilla-daemon
2013-12-09 13:41 ` bugzilla-daemon
2013-12-09 14:39 ` bugzilla-daemon
2013-12-10 6:55 ` bugzilla-daemon
2013-12-10 6:55 ` bugzilla-daemon
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=bug-66751-12968@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@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.