From: Yinghai Lu <yinghai@kernel.org>
To: Thomas Renninger <trenn@suse.de>
Cc: linux-kernel@vger.kernel.org, jbarnes@virtuousgeek.org,
akpm@linux-foundation.org, mingo@elte.hu
Subject: Re: IRQ regression messes up xseries 330 SCI resulting in apic=off - bisected to commit b9c61b70075c87a861262473
Date: Mon, 01 Feb 2010 12:36:59 -0800 [thread overview]
Message-ID: <4B673B6B.6060404@kernel.org> (raw)
In-Reply-To: <201002011559.07869.trenn@suse.de>
On 02/01/2010 06:59 AM, Thomas Renninger wrote:
> Hi,
>
> booting a latest kernel on this machine results in:
>
> PCI: PCI BIOS revision 2.10 entry at 0xfd61c, last bus=1
> PCI: Using configuration type 1 for base access bio: create slab <bio-0> at 0
> ACPI: SCI (IRQ30) allocation failed
> ACPI Exception: AE_NOT_ACQUIRED, Unable to install System Control Interrupt handler (20090903/evevent-161)
> ACPI: Unable to start the ACPI Interpreter
>
> Later all kind of devices fail...
>
...
>
>
> Attached are dmesg of an umodified broken 2.6.32 kernel and
> dmesg of a 2.6.32 kernel in which I reverted above patch (apic=verbose).
> The reverting needed some adjusting and I did this without understanding
> the code. I also attach the backported patch reverting above for 2.6.32
> which makes the machine work again (see dmesg attachment).
> This probably cannot go in, it would be great if someone could help
> finding a proper patch for mainline which makes the machine work again.
> (The ACPI irq, SCI, is meant to be on IRQ 30, rerouted from IRQ 3 via
> APIC source override table, which is rather odd/uncommon. Hope that helps)
ok, the root cause the SCI in on second ioapic....
will have a patch for it.
Thanks
Yinghai
next prev parent reply other threads:[~2010-02-01 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 14:59 Thomas Renninger
2010-02-01 20:36 ` Yinghai Lu [this message]
2010-02-02 1:16 ` Yinghai Lu
2010-02-02 8:03 ` Yinghai Lu
2010-02-02 9:59 ` Thomas Renninger
2010-02-02 18:30 ` [PATCH -v3] x86: fix sci on ioapic 1 Yinghai Lu
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=4B673B6B.6060404@kernel.org \
--to=yinghai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=trenn@suse.de \
/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
Powered by JetHome