From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>, Ingo Molnar <mingo@elte.hu>,
Alexey Starikovskiy <astarikovskiy@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
venkatesh.pallipadi@intel.com, Huang Ying <ying.huang@intel.com>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: v2.6.26-rc9: ACPI PCI irq routing on NUMA? + early_ioremap trouble
Date: Fri, 18 Jul 2008 13:59:12 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.55.0807181302020.12125@cliff.in.clinika.pl> (raw)
In-Reply-To: <19f34abd0807180051i544367b7s64f32d601af31296@mail.gmail.com>
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
next prev parent reply other threads:[~2008-07-18 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 13:47 Vegard Nossum
2008-07-17 18:45 ` Bjorn Helgaas
2008-07-17 20:58 ` Vegard Nossum
2008-07-18 0:47 ` Maciej W. Rozycki
2008-07-18 7:51 ` Vegard Nossum
2008-07-18 12:59 ` Maciej W. Rozycki [this message]
2008-07-18 12:26 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.55.0807181302020.12125@cliff.in.clinika.pl \
--to=macro@linux-mips.org \
--cc=andi@firstfloor.org \
--cc=astarikovskiy@suse.de \
--cc=bjorn.helgaas@hp.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=vegard.nossum@gmail.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®