From: rhn <kebuac.rhn@porcupinefactory.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: rhn <kebuac.rhn@porcupinefactory.org>,
kernel list <linux-kernel@vger.kernel.org>,
joeyli.kernel@gmail.com, linux-pm@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: Unreliable hibernation on Lenovo x230 (regression)
Date: Fri, 3 Apr 2015 17:58:25 +0200 [thread overview]
Message-ID: <20150403175825.79816fea@porcupinefactory.org> (raw)
In-Reply-To: <20150402152805.GA17021@amd>
On Thu, 2 Apr 2015 17:28:05 +0200
Pavel Machek <pavel@ucw.cz> wrote:
> On Wed 2015-04-01 21:47:43, rhn wrote:
> > Hello,
> >
> > Between kernel 3.16 and 3.17, a regression has been introduced where the first hibernation after regular shutdown always fails to resume. Subsequent hibernations succeed.
> >
> > The system is a Lenovo x230 with Intel i5, booting with EFI, with the hibernate partition located on a secondary SSD drive. Installed system is Fedora 20, hibernation and reboots were issued using the KDE shutdown dialog.
> >
> > I have tracked the problem to first appear in the commit
> > e67ee10190e69332f929bdd6594a312363321a66 Merge branches 'pm-sleep', 'pm-cpufreq' and 'pm-cpuidle'
> >
> > The problem itself manifests in dmesg as follows (system was first
> > restarted, then hibernated - this log is from the subsequent
> resume):
>
> Ok, can you try to disable cpufreq and cpuidle, and then try if it
> reproduces?
>
> At that point, this is the candidate:
>
> commit e67ee10190e69332f929bdd6594a312363321a66
> Merge: 21c806d 84c91b7 39c8bba 372ba8c
> Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Date: Mon Aug 11 23:19:48 2014 +0200
>
> Merge branches 'pm-sleep', 'pm-cpufreq' and 'pm-cpuidle'
>
> * pm-sleep:
> PM / hibernate: avoid unsafe pages in e820 reserved regions
>
> ...
> Alternatively, you can just try to revert
>
> commit 84c91b7ae07c62cf6dee7fde3277f4be21331f85
> Author: Lee, Chun-Yi <joeyli.kernel@gmail.com>
> Date: Mon Aug 4 23:23:21 2014 +0800
>
> PM / hibernate: avoid unsafe pages in e820 reserved regions
>
> When the machine doesn't well handle the e820 persistent when
> hibernate
> resuming, then it may cause page fault when writing image to
> snapshot
> buffer:
>
>
> ...
>
> Thanks,
> Pavel
I tried to disable CONFIG_CPU_IDLE and CONFIG_CPU_FREQ, however for some reason I could only disable CONFIG_CPU_FREQ.
The bug persisted.
Reverting the commit 84c91b7 on top of e67ee10 fixes the problem.
I created a copy of the bug report here: https://bugzilla.kernel.org/show_bug.cgi?id=96111
Cheers,
rhn
next prev parent reply other threads:[~2015-04-03 15:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150401214743.20fbe2c5@porcupinefactory.org>
2015-04-02 15:28 ` Unreliable hibernation on Lenovo x230 (regression) Pavel Machek
2015-04-02 16:50 ` joeyli
2015-04-02 17:22 ` joeyli
2015-04-02 18:12 ` rhn
2015-04-03 1:23 ` joeyli
2015-04-03 16:00 ` rhn
2015-04-03 15:58 ` rhn [this message]
2015-04-03 16:40 ` Pavel Machek
2015-04-03 21:43 ` Rafael J. Wysocki
2015-04-04 8:12 ` rhn
2015-04-05 7:24 ` joeyli
2015-04-05 7:51 ` Yinghai Lu
2015-04-06 7:12 ` Ingo Molnar
2015-04-05 7:26 ` joeyli
2015-04-06 23:28 ` Rafael J. Wysocki
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=20150403175825.79816fea@porcupinefactory.org \
--to=kebuac.rhn@porcupinefactory.org \
--cc=joeyli.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/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).