On Thu, 10 Aug 2017, Ingo Molnar wrote:
> * Vitaly Kuznetsov wrote:
> > I haven't received a single comment on this since the initial submission
> > on June, 26 - is it so bad? :-)
Sorry slipped through the cracks.
> So the fix looks good to me at first sight, but wanted to wait for Thomas to
>
Ingo Molnar writes:
> * Vitaly Kuznetsov wrote:
>
>> Vitaly Kuznetsov writes:
>>
>> > A hang on CPU0 onlining after a preceding offlining is observed. Trace
>> > shows that CPU0 is stuck in check_tsc_sync_target() waiting for source
>> > CPU to run check_tsc_sync_source() but this never happen
* Vitaly Kuznetsov wrote:
> Vitaly Kuznetsov writes:
>
> > A hang on CPU0 onlining after a preceding offlining is observed. Trace
> > shows that CPU0 is stuck in check_tsc_sync_target() waiting for source
> > CPU to run check_tsc_sync_source() but this never happens. Source CPU,
> > in its tur
Vitaly Kuznetsov writes:
> A hang on CPU0 onlining after a preceding offlining is observed. Trace
> shows that CPU0 is stuck in check_tsc_sync_target() waiting for source
> CPU to run check_tsc_sync_source() but this never happens. Source CPU,
> in its turn, is stuck on synchronize_sched() which
4 matches
Mail list logo