From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Andrew Worsley <amworsley@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
"Rafael J. Wysocki" <rafael@kernel.org>,
kernel list <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@vger.kernel.org>,
Len Brown <len.brown@intel.com>,
844788@bugs.debian.org
Subject: Re: 4.16-rc3 fails to resume on MacBookPro10,1 -
Date: Sun, 11 Mar 2018 11:25:33 +0100 [thread overview]
Message-ID: <1796290.BApLEM9bFY@aspire.rjw.lan> (raw)
In-Reply-To: <CA+Y=x3mwNDNJTt=n-K__wbCb8P+VhgMafRiofc0tnXqdgRk43w@mail.gmail.com>
On Sunday, March 11, 2018 5:52:47 AM CET Andrew Worsley wrote:
>
> --94eb2c04c64405d3da05671bccce
> Content-Type: text/plain; charset="UTF-8"
>
> On 11 March 2018 at 00:16, Pavel Machek <pavel@ucw.cz> wrote:
> > Hi!
> >
> >> > Ok, I've just tested linux-next, and it works ok for me on thinkpad
> >> > x60. (But that's probably rather different configuration from the
> >> > macbook).
> >> >
> >> > Unfortunately, I could not deduce anything useful from the
> >> > backtraces. Andrew, could you try v4.15 with KPTI disabled ?
> >> >
> >> > Thanks,
> >> > Pavel
> >>
> >> This is 4.15 kernel with KPTI disabled:
> >> % grep PAGE_TABLE .config
> >> # CONFIG_PAGE_TABLE_ISOLATION is not set
> >>
> >> As I expected it appears no more infomative to me.
> >>
> >> What I really need is some clue as to what is supposed to be happening
> >> at this point.
> >
> > You may want to add some printks to see where it hangs.
> >
> > But maybe before that, you may want to test CPU hotplug, and make sure
> > s2ram works, etc...
> >
> > Perhaps basic-pm-debugging.txt is good place to start?
> >
> > Best regards,
> > Pavel
> > --
>
> Ok - all the test modes work but a full s2ram hangs (never comes back)
> and obviously the resume full save to disk fails.
So there probably is a common cause to these failures and it most likely
is low-level.
It also seems to be specific to your system as S2RAM works for me w/
4.16-rc4 on a few machines and hibernation appears to work here too.
> I attach the following files:
>
> echo reboot > /sys/power/disk
> echo disk > /sys/power/state
> Then saved dmesg to file dmesg-reboot-disk-ok.txt
It is better to file a bug at bugzilla.kernel.org for these things,
as they don't always go through email in a good shape.
Thanks,
Rafael
next prev parent reply other threads:[~2018-03-11 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+Y=x3=U_zheHBxeNSzL9nSdXOZB7rs-JDNr36323uJ9Uhx0Hg@mail.gmail.com>
[not found] ` <CA+Y=x3=+kPXJRNYo91i4yJiqqVHDsMhn2pAwkmAH2LV3usd7Hg@mail.gmail.com>
2018-03-03 9:24 ` 4.16-rc3 fails to resume on MacBookPro10,1 - Pavel Machek
2018-03-03 10:00 ` Rafael J. Wysocki
2018-03-03 10:26 ` Pavel Machek
2018-03-03 20:45 ` Pavel Machek
[not found] ` <CA+Y=x3k5tsf+oxTo9YQv195XQpEECfqtFcbCoYGkJVCQsbjWpA@mail.gmail.com>
2018-03-10 13:16 ` Pavel Machek
[not found] ` <CA+Y=x3mwNDNJTt=n-K__wbCb8P+VhgMafRiofc0tnXqdgRk43w@mail.gmail.com>
2018-03-11 10:25 ` Rafael J. Wysocki [this message]
2018-03-11 10:34 ` Pavel Machek
2018-03-11 12:43 ` Andrew Worsley
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=1796290.BApLEM9bFY@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=844788@bugs.debian.org \
--cc=amworsley@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@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