From: Wilmer van der Gaast <wilmer@gaast.net>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Machine crashes right *after* ~successful resume
Date: Tue, 21 Oct 2014 22:40:40 +0100 [thread overview]
Message-ID: <5446D2D8.2090203@gaast.net> (raw)
In-Reply-To: <CAE9FiQWugqXZdZDhDyKofKRXH6EgVq6DJ0JphM6DZSdS5nMhbw@mail.gmail.com>
Hello,
Sorry for the delay, finally poked at this again. It looks like the
no_console_suspend flag was causing troubles, which I didn't really need
anyway with logging going to my serial port.
This is what I get now on the failing resume:
[ 112.879390] PM: resume of devices complete after 2239.905 msecs
[ 112.880068] r8169 0000:07:00.0 eth0: link up
[ 112.880078] Switched to clocksource hpet
[ 116.069248] PM: Finishing wakeup.
[ 116.072574] Restarting tasks ... done.
[ 116.076664] PM: calling nb rcu_pm_notify+0x0/0x60
[ 116.081439] PM: ... nb rcu_pm_notify+0x0/0x60 done
[ 116.086267] PM: calling nb cpu_hotplug_pm_callback+0x0/0x50
[ 116.088526] systemd[1]: Got notification message for unit
systemd-journald.service
[ 116.099442] PM: ... nb cpu_hotplug_pm_callback+0x0/0x50 done
[ 116.105099] PM: calling nb fw_pm_notify+0x0/0x150
[ 116.109812] PM: ... nb fw_pm_notify+0x0/0x150 done
[ 116.114623] PM: calling nb bsp_pm_callback+0x0/0x50
[ 116.119504] PM: ... nb bsp_pm_callback+0x0/0x50 done
And then nothing, and it's hung. Looks the same to me (apart from the
tsc issues + hpet switch) as a successful resume:
[ 95.499513] PM: resume of devices complete after 1240.115 msecs
[ 96.368940] r8169 0000:07:00.0 eth0: link up
[ 98.676455] PM: Finishing wakeup.
[ 98.679765] Restarting tasks ... done.
[ 98.683821] PM: calling nb rcu_pm_notify+0x0/0x60
[ 98.688524] PM: ... nb rcu_pm_notify+0x0/0x60 done
[ 98.692044] systemd[1]: Got notification message for unit
systemd-journald.service
[ 98.700897] PM: calling nb cpu_hotplug_pm_callback+0x0/0x50
[ 98.706470] PM: ... nb cpu_hotplug_pm_callback+0x0/0x50 done
[ 98.712132] PM: calling nb fw_pm_notify+0x0/0x150
[ 98.716848] PM: ... nb fw_pm_notify+0x0/0x150 done
[ 98.721644] PM: calling nb bsp_pm_callback+0x0/0x50
[ 98.726536] PM: ... nb bsp_pm_callback+0x0/0x50 done
Full logs in http://gaast.net/~wilmer/.lkml/bad3.17-patched-megadebug.txt
Wilmer v/d Gaast.
--
+-------- .''`. - -- ---+ + - -- --- ---- ----- ------+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net |
+--- -- - ` ---------------+ +------ ----- ---- --- -- - +
next prev parent reply other threads:[~2014-10-21 21:40 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 23:20 Machine crashes right *after* ~successful resume Wilmer van der Gaast
2014-10-12 14:30 ` Pavel Machek
2014-10-12 15:49 ` Wilmer van der Gaast
2014-10-12 20:40 ` Pavel Machek
2014-10-12 23:47 ` Wilmer van der Gaast
2014-10-13 15:06 ` Rafael J. Wysocki
2014-10-15 11:16 ` Wilmer van der Gaast
2014-10-15 13:58 ` Bjorn Helgaas
2014-10-15 18:39 ` Yinghai Lu
2014-10-15 23:34 ` Wilmer van der Gaast
2014-10-16 4:32 ` Yinghai Lu
2014-10-16 9:36 ` Wilmer van der Gaast
2014-10-16 16:36 ` Yinghai Lu
2014-10-16 21:08 ` Wilmer van der Gaast
2014-10-18 21:28 ` Yinghai Lu
2014-10-18 23:57 ` Wilmer van der Gaast
2014-10-19 4:29 ` Yinghai Lu
2014-10-19 10:48 ` Wilmer van der Gaast
2014-10-21 21:40 ` Wilmer van der Gaast [this message]
2014-10-21 23:15 ` Yinghai Lu
2014-10-22 12:53 ` Wilmer van der Gaast
2014-10-26 21:53 ` Yinghai Lu
2014-10-27 10:50 ` Wilmer van der Gaast
2014-10-27 18:23 ` Yinghai Lu
2014-10-27 22:22 ` Wilmer van der Gaast
2014-10-27 23:41 ` Yinghai Lu
2014-10-28 0:03 ` Wilmer van der Gaast
2014-10-28 1:12 ` Yinghai Lu
2014-10-28 4:03 ` Yinghai Lu
2014-10-28 10:23 ` Wilmer van der Gaast
2014-10-28 23:34 ` Wilmer van der Gaast
2014-10-29 5:17 ` Yinghai Lu
2014-10-29 9:37 ` Wilmer van der Gaast
2014-10-30 0:53 ` Yinghai Lu
2014-10-30 10:36 ` Wilmer van der Gaast
2014-10-30 16:57 ` Yinghai Lu
2014-10-30 21:54 ` Wilmer van der Gaast
2014-10-30 23:02 ` Yinghai Lu
2014-10-30 23:24 ` Wilmer van der Gaast
2014-10-31 0:43 ` Yinghai Lu
2014-10-31 2:13 ` Yinghai Lu
2014-10-31 9:39 ` Wilmer van der Gaast
2014-10-31 16:11 ` Yinghai Lu
2014-10-31 21:13 ` Wilmer van der Gaast
2014-10-31 21:22 ` Yinghai Lu
2014-10-31 23:18 ` Yinghai Lu
2014-11-01 0:00 ` Wilmer van der Gaast
2014-11-01 2:10 ` Yinghai Lu
2014-11-02 23:16 ` Wilmer van der Gaast
2014-10-27 21:21 ` Pavel Machek
2014-10-19 8:07 ` Pavel Machek
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=5446D2D8.2090203@gaast.net \
--to=wilmer@gaast.net \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=yinghai@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).