mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
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 09:51:02 +0200	[thread overview]
Message-ID: <19f34abd0807180051i544367b7s64f32d601af31296@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.55.0807180117320.6536@cliff.in.clinika.pl>

On Fri, Jul 18, 2008 at 2:47 AM, Maciej W. Rozycki <macro@linux-mips.org> 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

  reply	other threads:[~2008-07-18  7:51 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 [this message]
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=19f34abd0807180051i544367b7s64f32d601af31296@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --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=macro@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --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®