From: Pavel Machek <pavel@ucw.cz>
To: Woody Suwalski <terraluna977@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
kernel list <linux-kernel@vger.kernel.org>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com
Subject: Re: 4.10-rc1: thinkpad x60: who ate my cpu?
Date: Mon, 13 Feb 2017 09:02:15 +0100 [thread overview]
Message-ID: <20170213080215.GA3730@amd> (raw)
In-Reply-To: <161a3edb-84f1-769d-d8e9-04102ddbbe58@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]
Hi!
> >>>And now it is:
> >>>[692517.868523] ACPI: Preparing to enter system sleep state S3
> >>>[692518.172074] ACPI : EC: EC stopped
> >>>[692518.172076] PM: Saving platform NVS memory
> >>>[692518.172269] Disabling non-boot CPUs ...
> >>>[692518.172269] ACPI: Low-level resume complete
> >>>[692518.172269] ACPI : EC: EC started
> >>>[692518.172269] PM: Restoring platform NVS memory
> >>>[692518.172269] ACPI: Waking up from system sleep state S3
> >>>
> >>>Is there any test I could do on the CPU wakeup while in that state?
> >>>
> >>Is there a way to kick the offline-CPU into operation from /sys level?
> >echo 0 > /sys/devices/system/cpu/cpu1/online
> >
> >should work. And... good thinking :-).
> > Pavel
> Did not work,
> echo 0 > /sys/devices/system/cpu/cpu1/online
> -su: echo: write error: Device or resource busy
>
> However
> echo 1 > /sys/devices/system/cpu/cpu1/online
> did not return an error ( but still only CPU0 seen)
>
> Interesting experiment: I have hibernated and then woke up - and still only
> CPU0. I was expecting that after the power cycle the hotplug will bring CPU1
> up...
Which is interesting indeed. Hardware was powercycled, so what is
broken is probably some kernel state...
[Evil: /sys/devices/cpu/ -- some perf stuff.
/sys/devices/system/cpu -- that's where real CPU stuff is
hiding.]
cd /sys/devices/system/cpu/cpu1
while true; do echo 0 > online; echo 1 > online; done
...crashes x60 with 4.10-rc in few minutes. [Which is bad -- it should
not die, but also good -- this is easier to reproduce then running 100
suspend cycles.]
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 --]
next prev parent reply other threads:[~2017-02-13 8:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 22:17 4.10-rc1: thinkpad x60: who ate my cpu? Pavel Machek
2017-01-09 9:30 ` Pavel Machek
2017-01-13 1:19 ` Woody Suwalski
2017-01-14 11:30 ` Pavel Machek
2017-01-15 9:56 ` Pavel Machek
2017-02-11 23:48 ` Woody Suwalski
2017-02-12 15:43 ` Woody Suwalski
2017-02-12 19:57 ` Pavel Machek
2017-02-13 1:35 ` Woody Suwalski
2017-02-13 8:02 ` Pavel Machek [this message]
2017-02-13 8:48 ` Thomas Gleixner
2017-02-13 9:42 ` Pavel Machek
2017-02-13 10:18 ` lkml
2017-02-13 11:25 ` Thomas Gleixner
2017-02-13 11:39 ` lkml
2017-02-13 11:40 ` lkml
2017-02-13 11:53 ` 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=20170213080215.GA3730@amd \
--to=pavel@ucw.cz \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=terraluna977@gmail.com \
--cc=tglx@linutronix.de \
/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).