From: Pavel Machek <pavel@ucw.cz>
To: Woody Suwalski <terraluna977@gmail.com>
Cc: linux-kernel@vger.kernel.org, rafael.j.wysocki@intel.com,
Linux-pm mailing list <linux-pm@vger.kernel.org>
Subject: Re: Thinkpad x60 hibernate broken on 4.13+
Date: Wed, 27 Dec 2017 18:59:17 +0100 [thread overview]
Message-ID: <20171227175917.GA9749@amd> (raw)
In-Reply-To: <25febf9d-5d45-a7fc-f5c9-4d3bb2828237@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
Hi!
> Merry Christmas all,
> Following Pavel's example I have exercised my Thinkpad x60, and noticed that
> hibernation is broken - it does hibernate, but upon wakeup it goes through
> restore image 80%, and then black screen and dead system. But the fan _is_
> running, so I guess CPU is doing something.
>
> I have only done some rudimentary tests:
> 4.12.3 and 4.12.9 are OK.
> 4.13.3 and 4.13.12 bad
> 4.14.5 and 4.14.9 bad
> 4.15-rc5 bad
> Pavel, can you duplicate the issue? All I did to trigger was "systemctl
> hibernate".
I'm sorry, debugging that is not easy for me at the moment.
> Bisecting will be slow as I build the 32-bit kernels in a VM nowadays...
You should be able to build on x86-64 with right .config...
Before bisect, I'd suggest:
a) testing suspend. That should work in 4.13 and 4.14
b) maybe testing with minimal drivers to see if it is one of the
drivers breaking it.
Oh and there's file in Documentation/ describing hibernation
debugging. You should be able to locate bad driver without bisect.
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
parent reply other threads:[~2017-12-27 17:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <25febf9d-5d45-a7fc-f5c9-4d3bb2828237@gmail.com>]
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=20171227175917.GA9749@amd \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=terraluna977@gmail.com \
/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).