From: Thomas Renninger <trenn@suse.de>
To: Yinghai Lu <yinghai@kernel.org>
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: Tue, 2 Feb 2010 10:59:18 +0100 [thread overview]
Message-ID: <201002021059.18939.trenn@suse.de> (raw)
In-Reply-To: <4B67DC58.7060809@kernel.org>
On Tuesday 02 February 2010 09:03:36 Yinghai Lu wrote:
> On 02/01/2010 05:16 PM, Yinghai Lu wrote:
> > 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
> >>
> >
> > please check
>
> Subject: [PATCH -v2] x86: fix sci on ioapic 1
Works for me, thanks!
Tested-by: Thomas Renninger <trenn@suse.de>
Is this supposed to go into 2.6.33 still?
Do you consider this save enough to CC: stable@kernel.org and just
push it/commit it there?
I can confirm that this one patches and works fine for 2.6.32.
2.6.31 would also need this fix, the regression was introduced somewhere
between 2.6.30 and 2.6.31.
Thanks again,
Thomas
next prev parent reply other threads:[~2010-02-02 9:59 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
2010-02-02 1:16 ` Yinghai Lu
2010-02-02 8:03 ` Yinghai Lu
2010-02-02 9:59 ` Thomas Renninger [this message]
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=201002021059.18939.trenn@suse.de \
--to=trenn@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yinghai@kernel.org \
/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®