On 04/11/2013 01:40 PM, Thomas Gleixner wrote:
> On Wed, 10 Apr 2013, Srivatsa S. Bhat wrote:
>
>> Interestingly, in every single stack trace, the crashing task is the
>> migration
>> thread. Now, migration thread belongs to the highest priority stop_task sched
>> class, and this particular
On Wed, 10 Apr 2013, Srivatsa S. Bhat wrote:
> Interestingly, in every single stack trace, the crashing task is the migration
> thread. Now, migration thread belongs to the highest priority stop_task sched
> class, and this particular sched class is very unique in the way it implements
> its
On Wed, 10 Apr 2013, Srivatsa S. Bhat wrote:
Interestingly, in every single stack trace, the crashing task is the migration
thread. Now, migration thread belongs to the highest priority stop_task sched
class, and this particular sched class is very unique in the way it implements
its internal
On 04/11/2013 01:40 PM, Thomas Gleixner wrote:
On Wed, 10 Apr 2013, Srivatsa S. Bhat wrote:
Interestingly, in every single stack trace, the crashing task is the
migration
thread. Now, migration thread belongs to the highest priority stop_task sched
class, and this particular sched class is
ps?
Regards,
Srivatsa S. Bhat
-->
From: Srivatsa S. Bhat
Subject: [PATCH] CPU hotplug, smpboot: Fix crash in smpboot_thread_fn()
Dave Hansen and Borislav Petkov reported the following crash, which
corresponds the following BUG_ON in smp
--
From: Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com
Subject: [PATCH] CPU hotplug, smpboot: Fix crash in smpboot_thread_fn()
Dave Hansen and Borislav Petkov reported the following crash, which
corresponds the following BUG_ON in smpboot_thread_fn
6 matches
Mail list logo
