Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1562648
| From | Mike Galbraith <efault@gmx.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: tip.today - scheduler bam boom crash (cpu hotplug) |
| Date | 2017-01-19 12:50 +0100 |
| Message-ID | <t1jo6-10B-25@gated-at.bofh.it> (permalink) |
| References | <t1fua-70y-5@gated-at.bofh.it> <t1iim-n0-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
tip.today - scheduler bam boom crash (cpu hotplug) Mike Galbraith <efault@gmx.de> - 2017-01-19 08:40 +0100
Re: tip.today - scheduler bam boom crash (cpu hotplug) Peter Zijlstra <peterz@infradead.org> - 2017-01-19 11:40 +0100
Re: tip.today - scheduler bam boom crash (cpu hotplug) Mike Galbraith <efault@gmx.de> - 2017-01-19 12:50 +0100
Re: tip.today - scheduler bam boom crash (cpu hotplug) Peter Zijlstra <peterz@infradead.org> - 2017-01-19 14:40 +0100
Re: tip.today - scheduler bam boom crash (cpu hotplug) Ingo Molnar <mingo@kernel.org> - 2017-01-19 18:00 +0100
Re: tip.today - scheduler bam boom crash (cpu hotplug) Peter Zijlstra <peterz@infradead.org> - 2017-01-19 18:30 +0100
Re: sched/clock: Fix hotplug issue kbuild test robot <lkp@intel.com> - 2017-01-19 21:40 +0100
Re: sched/clock: Fix hotplug issue kbuild test robot <lkp@intel.com> - 2017-01-19 21:50 +0100
[tip:sched/core] sched/clock: Fix hotplug crash tip-bot for Peter Zijlstra <tipbot@zytor.com> - 2017-01-20 08:50 +0100
csiph-web