[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6fd4e2d2-c0ac-b26d-9a14-0379b4421679@kernel.org>
Date: Thu, 18 Oct 2018 16:08:27 -0400
From: Sinan Kaya <okaya@...nel.org>
To: "Guilherme G. Piccoli" <gpiccoli@...onical.com>,
linux-pci@...r.kernel.org, kexec@...ts.infradead.org,
x86@...nel.org
Cc: linux-kernel@...r.kernel.org, bhelgaas@...gle.com,
dyoung@...hat.com, bhe@...hat.com, vgoyal@...hat.com,
tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, hpa@...or.com,
andi@...stfloor.org, lukas@...ner.de, billy.olsen@...onical.com,
cascardo@...onical.com, ddstreet@...onical.com,
fabiomirmar@...onical.com, gavin.guo@...onical.com,
jay.vosburgh@...onical.com, kernel@...ccoli.net, mfo@...onical.com,
shan.gavin@...ux.alibaba.com
Subject: Re: [PATCH 3/3] x86/quirks: Add parameter to clear MSIs early on boot
On 10/18/2018 2:37 PM, Guilherme G. Piccoli wrote:
> We observed a kdump failure in x86 that was narrowed down to MSI irq
> storm coming from a PCI network device. The bug manifests as a lack of
> progress in the boot process of kdump kernel, and a flood of kernel
> messages like:
>
> [...]
> [ 342.265294] do_IRQ: 0.155 No irq handler for vector
> [ 342.266916] do_IRQ: 0.155 No irq handler for vector
> [ 347.258422] do_IRQ: 14053260 callbacks suppressed
> [...]
These kind of issues are usually fixed by fixing the network driver's
shutdown routine to ensure that MSI interrupts are cleared there.
Powered by blists - more mailing lists