On Thu, Oct 22 2020 at 13:56, Pingfan Liu wrote:
> I hit a irqflood bug on powerpc platform, and two years ago, on a x86 platform.
> When the bug happens, the kernel is totally occupies by irq. Currently, there
> may be nothing or just soft lockup warning showed in console. It is better
> to warn users with irq flood info.
>
> In the kdump case, the kernel can move on by suppressing the irq flood.
You're curing the symptom not the cause and the cure is just magic and
can't work reliably.
Where is that irq flood originated from and why is none of the
mechanisms we have in place to shut it up working?
Thanks,
tglx
