[opensuse-kernel] what does "rerouted to legacy IRQ" mean and how do I prevent it?
I'm having a few odd issues with 12.1+updates on an HP ML570G3 box. I'm pretty certain it's irq related - in 12.1 (kernel 3.1.9-1.4) the irqs for the two storage controllers and the two GigE NICs are "rerouted to legacy IRQs". In 11.4 this does not happen - what does this rerouting mean and is there a way of preventing it in 12.1? thanks -- Per Jessen, Zürich (13.6°C) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Thursday, April 19, 2012 03:55:57 PM Per Jessen wrote:
I'm having a few odd issues with 12.1+updates on an HP ML570G3 box. I'm pretty certain it's irq related - in 12.1 (kernel 3.1.9-1.4) the irqs for the two storage controllers and the two GigE NICs are "rerouted to legacy IRQs". In 11.4 this does not happen - what does this rerouting mean and is there a way of preventing it in 12.1?
You hit an IRQ quirk/workaround which seem to be necessary on specific chipsets. It might not be on yours and if you see any negative impact (no msi for this device?) you can revert the recent changes via boot param. In fact there are 2 boot params: - noioapicreroute # disables more or less only the quirk you mention - noioapicquirk # disables the workaround you see, plus possible other # workarounds which may (or not) be needed for # your platform I'd try: noioapicquirk -> if all devices still work as expected you are fine, if not, try: noioapicreroute Thomas -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Thomas Renninger wrote:
On Thursday, April 19, 2012 03:55:57 PM Per Jessen wrote:
I'm having a few odd issues with 12.1+updates on an HP ML570G3 box. I'm pretty certain it's irq related - in 12.1 (kernel 3.1.9-1.4) the irqs for the two storage controllers and the two GigE NICs are "rerouted to legacy IRQs". In 11.4 this does not happen - what does this rerouting mean and is there a way of preventing it in 12.1?
You hit an IRQ quirk/workaround which seem to be necessary on specific chipsets. It might not be on yours and if you see any negative impact (no msi for this device?) you can revert the recent changes via boot param.
Hi Thomas I saw a few weird things - both RAID controllers and both GigE interfaces were affected. See bug#757778.
In fact there are 2 boot params: - noioapicreroute # disables more or less only the quirk you mention
- noioapicquirk # disables the workaround you see, plus possible other # workarounds which may (or not) be needed for # your platform
I'd try: noioapicquirk -> if all devices still work as expected you are fine, if not, try: noioapicreroute
thanks for the advice, I used 'pci=noioapicquirk' which did the trick. -- Per Jessen, Zürich (11.3°C) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (2)
-
Per Jessen -
Thomas Renninger