From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 65671] New: Problems with hibernation, with bisect
Date: Sun, 24 Nov 2013 22:38:32 +0000 [thread overview]
Message-ID: <bug-65671-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=65671
Bug ID: 65671
Summary: Problems with hibernation, with bisect
Product: Power Management
Version: 2.5
Kernel Version: 3.12
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: cpufreq@vger.kernel.org
Reporter: higuita@gmx.net
Regression: No
After upgrading the kernel to 3.12, i found that hibernation stop working. Most
of the time it gives IO errors writing the swap on hibernation, and when it
manage to do that, it crash all apps after the wakeup and remount the
filesystem as read-only
As 3.11.8 hibernation worked fine, i have done a bisect and found that the
problem show up in this commit:
commit 4a511de96d692f2dfa126c10dda4e41636c0ef27
Author: Mark Brown <broonie@linaro.org>
Date: Tue Aug 13 14:58:24 2013 +0200
cpufreq: cpufreq-cpu0: NULL is a valid regulator
Since NULL could in theory be a valid regulator we ought to check for
IS_ERR() rather than for NULL. In practice this is unlikely to be an
issue but it's better for neatness.
Signed-off-by: Mark Brown <broonie@linaro.org>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
:040000 040000 3e8d03d2dc170492ba9f0311ef9156344452f6de
fb5d9ad67f332dec478a68cbd9387b15381584ce M drivers
Kernel 3.12.1 still have the problem
i'm using slackware64 14.1 with gcc 4.8.2
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2013-11-24 22:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 22:38 bugzilla-daemon [this message]
2013-11-24 23:49 ` [Bug 65671] Problems with hibernation, with bisect bugzilla-daemon
2013-11-25 1:18 ` bugzilla-daemon
2013-11-25 2:49 ` bugzilla-daemon
2013-11-25 11:16 ` bugzilla-daemon
2013-11-25 17:08 ` bugzilla-daemon
2013-12-01 18:08 ` bugzilla-daemon
2013-12-02 2:11 ` bugzilla-daemon
2013-12-03 0:57 ` [Bug 65671] hibernation - IO errors writing to swap, crashing apps, 3,11.8 worked bugzilla-daemon
2013-12-05 23:37 ` bugzilla-daemon
2013-12-06 1:59 ` bugzilla-daemon
2013-12-19 11:56 ` bugzilla-daemon
2013-12-27 11:42 ` bugzilla-daemon
2014-02-24 3:17 ` bugzilla-daemon
2014-03-25 0:25 ` [Bug 65671] hibernation - IO errors writing to swap, crashing apps, 3,11.8 worked, unless rmmod powernow_k8 bugzilla-daemon
2014-04-30 21:07 ` bugzilla-daemon
2014-04-30 21:10 ` bugzilla-daemon
2014-05-09 1:59 ` bugzilla-daemon
2014-08-04 1:51 ` [Bug 65671] Asus A8V deluxe(AMD): " bugzilla-daemon
2014-09-09 15:03 ` 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-65671-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).