From: lkml@pengaru.com
To: Pavel Machek <pavel@ucw.cz>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Woody Suwalski <terraluna977@gmail.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
kernel list <linux-kernel@vger.kernel.org>,
mingo@redhat.com, hpa@zytor.com
Subject: Re: 4.10-rc1: thinkpad x60: who ate my cpu?
Date: Mon, 13 Feb 2017 04:18:51 -0600 [thread overview]
Message-ID: <20170213101851.GX3712@shells.gnugeneration.com> (raw)
In-Reply-To: <20170213094236.GA2924@amd>
On Mon, Feb 13, 2017 at 10:42:36AM +0100, Pavel Machek wrote:
> Hi!
>
> On Mon 2017-02-13 09:48:41, Thomas Gleixner wrote:
> > On Mon, 13 Feb 2017, Pavel Machek wrote:
> > > 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.]
> >
> > Can you tell where it crashes?
>
> I did not expect a crash, so I was in X... I have a feeling that this
> will be reproducible on a lot of hardware, but let me try.
FYI: Lockup reproduced with 4.10.0-rc7 with an X61s.
Caught a glimpse of something about an RCU stall timeout before the system shut
off. Prior to that, during the loop execution, a bunch of systemd processes
were experiencing watchdog timeouts, and procps `top` would start but
never refresh, leaving the CPU column all "nan".
Regards,
Vito Caputo
next prev parent reply other threads:[~2017-02-13 10:18 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
2017-02-13 8:48 ` Thomas Gleixner
2017-02-13 9:42 ` Pavel Machek
2017-02-13 10:18 ` lkml [this message]
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=20170213101851.GX3712@shells.gnugeneration.com \
--to=lkml@pengaru.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.