From: Mike Galbraith <efault@gmx.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: tip.today - scheduler bam boom crash (cpu hotplug)
Date: Thu, 19 Jan 2017 12:39:06 +0100 [thread overview]
Message-ID: <1484825946.17735.7.camel@gmx.de> (raw)
In-Reply-To: <20170119101924.GJ6485@twins.programming.kicks-ass.net>
On Thu, 2017-01-19 at 11:19 +0100, Peter Zijlstra wrote:
> OK, you also forgot to tell what you did to trigger this, but a little
> playing around seems enough to reproduce. All that was required was
> offline + online and *boom*.
Oh, sorry, it was Steven's hotplug stress script. I thought the first
couple lines of kernel output (+$subject) told the tale.
next prev parent reply other threads:[~2017-01-19 11:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 7:31 tip.today - scheduler bam boom crash (cpu hotplug) Mike Galbraith
2017-01-19 10:19 ` Peter Zijlstra
2017-01-19 11:39 ` Mike Galbraith [this message]
2017-01-19 13:36 ` Peter Zijlstra
2017-01-19 16:54 ` Ingo Molnar
2017-01-19 17:20 ` Peter Zijlstra
2017-01-19 20:35 ` sched/clock: Fix hotplug issue kbuild test robot
2017-01-19 20:37 ` kbuild test robot
2017-01-20 6:36 ` [tip:sched/core] sched/clock: Fix hotplug crash tip-bot for Peter Zijlstra
2017-02-27 12:30 ` tip.today - scheduler bam boom crash (cpu hotplug) Wanpeng Li
2017-02-27 12:35 ` Paolo Bonzini
2017-02-27 12:43 ` Peter Zijlstra
2017-02-27 12:50 ` Paolo Bonzini
2017-02-27 13:04 ` Peter Zijlstra
2017-02-27 15:27 ` Paolo Bonzini
2017-02-27 15:59 ` Peter Zijlstra
2017-02-27 16:11 ` Paolo Bonzini
2017-02-27 16:36 ` Peter Zijlstra
2017-02-27 17:27 ` Paolo Bonzini
2017-02-27 17:40 ` Thomas Gleixner
2017-02-27 19:06 ` Paolo Bonzini
2017-02-27 20:35 ` Peter Zijlstra
2017-02-28 1:51 ` Wanpeng Li
2017-02-28 8:08 ` Peter Zijlstra
2017-02-28 8:11 ` Wanpeng Li
2017-03-01 13:39 ` Wanpeng Li
2017-03-01 14:17 ` Peter Zijlstra
2017-02-27 13:48 ` Wanpeng Li
2017-02-27 14:05 ` Peter Zijlstra
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=1484825946.17735.7.camel@gmx.de \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--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