On 18/10/2018 17:08, Sinan Kaya wrote: > 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. Sinan, I'm not sure shutdown handlers for drivers are called in panic kexec (I remember of an old experiment I did, loading a kernel with "kexec -p" didn't trigger the handlers). But this case is even worse, because the NICs were in PCI passthrough mode, using vfio. So, they were completely unaware of what happened in the host kernel. Also, this is spec compliant - system reset events should guarantee the bits are cleared (although kexec is not exactly a system reset, it's similar) Cheers, Guilherme
