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 01:47:44 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.55.0807180117320.6536@cliff.in.clinika.pl> (raw)
In-Reply-To: <19f34abd0807171358p3c5a44f9i91ab23d3f5e9671f@mail.gmail.com>
On Thu, 17 Jul 2008, Vegard Nossum wrote:
> Hah, I actually managed to get netconsole working. This is the log
> that fails (v2.6.26):
>
> http://folk.uio.no/vegardno/linux/numa-netconsole.txt
>
> I think this looks really interesting:
>
> [ 0.093562] ExtINT not setup in hardware but reported by MP table
> [ 0.093854] ENABLING IO-APIC IRQs
> [ 0.094244] ..TIMER: vector=0x31 apic1=-1 pin1=2 apic2=-1 pin2=0
> [ 0.094985] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> [ 0.094985] ...trying to set up timer (IRQ0) through the 8259A ...
> [ 0.094985] ..... (found pin 0) ...<7>APIC error on CPU0: 00(80)
> [ 0.094985] failed.
> [ 0.094985] ...trying to set up timer as Virtual Wire IRQ...<7>APIC
> error on CPU0: 80(80)
> [ 0.105761] works.
>
> This error would be:
> 7: Illegal register address
>
> 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.
Maciej
patch-next-2.6.26-rc9-20080711-apic-dprintk-0
diff -up --recursive --new-file linux-next-2.6.26-rc9-20080711.macro/include/asm-x86/apic.h linux-next-2.6.26-rc9-20080711/include/asm-x86/apic.h
--- linux-next-2.6.26-rc9-20080711.macro/include/asm-x86/apic.h 2008-07-16 14:50:07.000000000 +0000
+++ linux-next-2.6.26-rc9-20080711/include/asm-x86/apic.h 2008-07-18 00:33:19.000000000 +0000
@@ -10,7 +10,7 @@
#define ARCH_APICTIMER_STOPS_ON_C3 1
-#define Dprintk(x...)
+#define Dprintk printk
/*
* Debugging macros
next prev parent reply other threads:[~2008-07-18 0:48 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 [this message]
2008-07-18 7:51 ` Vegard Nossum
2008-07-18 12:59 ` Maciej W. Rozycki
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.0807180117320.6536@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®