From: Nikolaus Rath <Nikolaus@rath.org>
To: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Help with debugging intermittent crash on resume from hibernation
Date: Fri, 13 Mar 2015 20:02:45 -0700 [thread overview]
Message-ID: <8761a3s1vq.fsf@vostro.rath.org> (raw)
Hello,
In about one out of 10 resumes from hibernation, my system resets after
the hibernation image has been loaded. I am hibernating using
# echo platform > /sys/power/disk
# echo disk > /sys/power/state
When testing hibernation using
# echo core > /sys/power/pm_test
# echo platform > /sys/power/disk
# echo disk > /sys/power/state
I was not able to produce the same failure.
I then tried attaching a serial console and booted with
console=ttyS0,115200n8 no_console_suspend. For the failed attempt, the
last messages before the reset are:
[ 25.192978] Disabling non-boot CPUs ...
[ 25.234496] intel_pstate CPU 1 exiting
[ 25.270548] NOHZ: local_softirq_pending 10
[ 25.274657] NOHZ: local_softirq_pending 10
[ 25.279892] smpboot: CPU 1 is now offline
[ 25.318618] intel_pstate CPU 2 exiting
[ 25.454816] smpboot: CPU 2 is now offline
[ 25.494879] intel_pstate CPU 3 exiting
[ 25.647097] smpboot: CPU 3 is now offline
[ 25.687158] intel_pstate CPU 4 exiting
[ 25.819349] smpboot: CPU 4 is now offline
[ 25.859411] intel_pstate CPU 5 exiting
[ 25.995610] smpboot: CPU 5 is now offline
[ 26.015640] intel_pstate CPU 6 exiting
[ 26.155843] smpboot: CPU 6 is now offline
[ 26.175874] intel_pstate CPU 7 exiting
[ 26.201040] smpboot: CPU 7 is now offline
For the successful attempt, the last messages before the jump in the
time (which I assume indicate that resume was complete) are:
[ 25.428213] Disabling non-boot CPUs ...^M
[ 25.549875] intel_pstate CPU 1 exiting^M
[ 25.694081] smpboot: CPU 1 is now offline^M
[ 27.092141] intel_pstate CPU 2 exiting^M
[ 27.232341] smpboot: CPU 2 is now offline^M
[ 27.364542] intel_pstate CPU 3 exiting^M
[ 27.404597] NOHZ: local_softirq_pending 10^M
[ 27.408704] NOHZ: local_softirq_pending 10^M
[ 27.413942] smpboot: CPU 3 is now offline^M
[ 27.556820] intel_pstate CPU 4 exiting^M
[ 27.582000] smpboot: CPU 4 is now offline^M
[ 27.600891] intel_pstate CPU 5 exiting^M
[ 27.745093] smpboot: CPU 5 is now offline^M
[ 27.849247] intel_pstate CPU 6 exiting^M
[ 28.538259] smpboot: CPU 6 is now offline^M
[ 28.558292] intel_pstate CPU 7 exiting^M
[ 28.583457] smpboot: CPU 7 is now offline^M
[23880.929604] Enabling non-boot CPUs ...^M
[23880.933432] x86: Booting SMP configuration:^M
(I uploaded the complete logs to https://dl.dropboxusercontent.com/u/11545826/logfiles.tar.xz).
At least to me, this unfortunately gives absolutely no indication of
what might be going wrong.
Other than trying again with the -rc3 (which I'll do next), is there
anything else I can do to debug this further?
Thanks,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
next reply other threads:[~2015-03-14 3:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 3:02 Nikolaus Rath [this message]
2015-03-20 3:21 ` Help with debugging intermittent crash on resume from hibernation Nikolaus Rath
2015-03-20 3:57 ` Mike Galbraith
2015-04-18 3:15 ` Nikolaus Rath
2015-04-18 4:01 ` Mike Galbraith
2015-04-18 4:13 ` Nikolaus Rath
2015-04-18 4:45 ` Mike Galbraith
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=8761a3s1vq.fsf@vostro.rath.org \
--to=nikolaus@rath.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@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).