There is a SUSE bug here, but it has not have much details: IRQs rerouted to legacy IRQ https://bugzilla.novell.com/show_bug.cgi?id=757778 Relevant part is that Per sees this message: "rerouted to legacy IRQ" introduced in 3.1 via commit d7f6169a0d32002 in dmesg and has problems installing the machine. In comment #7 he states that disabling the quirk helps: "Following the advice of Thomas Renninger, I've added "pci=noioapicquirk" which makes the system behave as normally."
I can confirm that using "pci=noioapicquirk" makes the target system behave normally, i.e. irqs are not rerouted to legacy. Please let me know what sort of information/diagnostics you require.
*** This bug has been marked as a duplicate of bug 43074 ***
Per, please provide the output of "lspci -nn -v". Thanks!
Created attachment 73078 [details] output of "lspci -nn -v"
This rerouting issue is weird. X86_REROUTE_FOR_BROKEN_BOOT_IRQS compile option looks wrong and (no)ioapicreroute boot parameters seem to be not needed (noioapicquirk) should be used instead. This doesn't solve Per's problem, he would still need noioapicquirk. But it's still worthful cleanup. What do you think about these?
Created attachment 73372 [details] [PATCH 1/3] X86 PCI: Remove unneeded CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS compile option
Created attachment 73373 [details] [PATCH 2/3] X86 PCI: Remove unneeded noioapicreroute boot parameter
Created attachment 73374 [details] [PATCH 3/3] ACPI PCI: Cleanup indentation Not sure this one is worth it.
(In reply to comment #5) > This rerouting issue is weird. > X86_REROUTE_FOR_BROKEN_BOOT_IRQS compile option looks wrong This is exactly doing what it is supposed to. Gives the option to enable/disable the boot interrupt quirks at the cost of additional IRQ sharing. This should stay as is. > and > (no)ioapicreroute boot parameters seem to be not needed (noioapicquirk) > should > be used instead. I don't think so. There's a difference between them. noioapicquirk disables the quirks completely, while noioapicreroute only prevents rerouting. Some users may only want to disable rerouting and keep the other quirks alive. Different quirks handle different devices. I'm fine with 3/3. Let's wait until we figured out Pers issue before we do any cleanup, ok?
Btw, I think this boils down to an issue with tg3 as the cciss issue is solve by http://marc.info/?l=linux-kernel&m=132249697801585&w=2 according to Per.
Per, please provide the output of - ethtool -i <ethX> - ethtool -t <ethX> when tg3 is malfunctioning.
Hi Stephan I'll see what I can do - I need to upgrade to kernel 3.4.2 anyway.