On Fri, Jul 18, 2008 at 2:47 AM, Maciej W. Rozycki <macro@xxxxxxxxxxxxxx> wrote: >> Looks like APIC was misconfigured, which might explain IRQ routing weirdness? > > Here pin1 and pin2 have been correctly initialised, but apic1 and apic2 > are both set to -1. This is an "impossible scenario." Because of that > I/O APIC code actually pokes at random registers of the local APIC which > immediately precedes I/O APIC #0 in the fixmap. Results may be arbitrary. > >> Will try to provide the booting one later. Now zZz... > > Your system uses an MP table and there were quite a lot of changes in its > support code recently. A bug must have crept in. Please try the appended > patch and the "apic=debug" option for both cases and the resulting logs > may shed some light. I have done this for the bad case: http://folk.uio.no/vegardno/linux/netconsole2.txt (I added a warning for certain APIC errors as well. Not that it adds much in this particular case, but I think it would be good to have in mainline anyway, to highlight these error cases in the future...) Vegard -- "The animistic metaphor of the bug that maliciously sneaked in while the programmer was not looking is intellectually dishonest as it disguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036 -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
