On Tue, 30 Jan 2018 15:35:54 +1100
Michael Ellerman wrote:
> alexander.le...@verizon.com writes:
>
> > On Thu, Dec 14, 2017 at 12:10:39AM +1100, Michael Ellerman wrote:
> >>alexander.le...@verizon.com writes:
> >>
> >>> From: Nicholas Piggin
> >>>
> >>> [ Upstream commit 064996d62a33ffe1026
alexander.le...@verizon.com writes:
> On Thu, Dec 14, 2017 at 12:10:39AM +1100, Michael Ellerman wrote:
>>alexander.le...@verizon.com writes:
>>
>>> From: Nicholas Piggin
>>>
>>> [ Upstream commit 064996d62a33ffe10264b5af5dca92d54f60f806 ]
>>>
>>> The SMP hardlockup watchdog cross-checks other CP
On Thu, Dec 14, 2017 at 12:10:39AM +1100, Michael Ellerman wrote:
>alexander.le...@verizon.com writes:
>
>> From: Nicholas Piggin
>>
>> [ Upstream commit 064996d62a33ffe10264b5af5dca92d54f60f806 ]
>>
>> The SMP hardlockup watchdog cross-checks other CPUs for lockups, which
>> causes xmon headaches
alexander.le...@verizon.com writes:
> From: Nicholas Piggin
>
> [ Upstream commit 064996d62a33ffe10264b5af5dca92d54f60f806 ]
>
> The SMP hardlockup watchdog cross-checks other CPUs for lockups, which
> causes xmon headaches because it's assuming interrupts hard disabled
> means no watchdog troubl
From: Nicholas Piggin
[ Upstream commit 064996d62a33ffe10264b5af5dca92d54f60f806 ]
The SMP hardlockup watchdog cross-checks other CPUs for lockups, which
causes xmon headaches because it's assuming interrupts hard disabled
means no watchdog troubles. Try to improve that by calling
touch_nmi_watc
5 matches
Mail list logo