[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.55.0807181302020.12125@cliff.in.clinika.pl>
Date: Fri, 18 Jul 2008 13:59:12 +0100 (BST)
From: "Maciej W. Rozycki" <macro@...ux-mips.org>
To: Vegard Nossum <vegard.nossum@...il.com>
cc: Bjorn Helgaas <bjorn.helgaas@...com>, Ingo Molnar <mingo@...e.hu>,
Alexey Starikovskiy <astarikovskiy@...e.de>,
Thomas Gleixner <tglx@...utronix.de>,
venkatesh.pallipadi@...el.com, Huang Ying <ying.huang@...el.com>,
Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org
Subject: Re: v2.6.26-rc9: ACPI PCI irq routing on NUMA? + early_ioremap
trouble
On Fri, 18 Jul 2008, Vegard Nossum wrote:
> I have done this for the bad case:
> http://folk.uio.no/vegardno/linux/netconsole2.txt
Thanks. The MP table looks broken:
Bus #4 is ISA
I/O APIC #32 Version 32 at 0xFEC00000.
Int: type 3, pol 1, trig 1, bus 4, IRQ 00, APIC ID 2, APIC INT 00
etc. (notice the different I/O APIC IDs reported), so any changes to our
code are not at fault. I suggest you ask your vendor to fix it up (did
they test it at all? -- it has no chance to work) or stick to ACPI (I can
see it has been automatically disabled for some reason).
Anyway, the piece of I/O APIC code in question should not poke at the
local APIC, so I'll prepare a fix to make it check for the APIC ID being
-1.
> (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...)
It might be useful indeed.
Maciej
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists