Backport request

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Folks!

There are more and more people worried about these usually harmless
warnings:

	do_IRQ: 0.39 No irq handler for vector

It took a while to figure out why that happens and why it is harmless for
most interrupts, but there is also a real issue hidden for level type
IOAPIC interrupts.

The following commits in Linus tree are addressing the issue:

 b7107a67f0d1 ("x86/irq: Handle spurious interrupt after shutdown gracefully")
 dfe0cf8b51b0 ("x86/ioapic: Implement irq_get_irqchip_state() callback")
 62e0468650c3 ("genirq: Add optional hardware synchronization for shutdown")
 1d21f2af8571 ("genirq: Fix misleading synchronize_irq() documentation")
 4001d8e8762f ("genirq: Delay deactivation in free_irq()")

There is another one which makes sense to be backported:

 f8a8fe61fec8 ("x86/irq: Seperate unused system vectors from spurious entry again")

These should go back to 4.19, but not farther.

They apply cleanly to 5.1 and 5.2. A backport to 4.19 is attached.

Thanks,

	tglx

Attachment: patches-4.19.tar.bz2
Description: Binary data


[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux