From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Len Brown <lenb@kernel.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Jason Vas Dias <jason.vas.dias@gmail.com>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH] x86 ACPI: Blacklist two HP machines with buggy BIOSes (Re: 2.6.27-rc8+ - first impressions)
Date: Mon, 6 Oct 2008 19:15:10 +0200 [thread overview]
Message-ID: <200810061915.11936.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.2.00.0810060749570.3208@nehalem.linux-foundation.org>
On Monday, 6 of October 2008, Linus Torvalds wrote:
>
> On Mon, 6 Oct 2008, Rafael J. Wysocki wrote:
> >
> > Unfortunately some of the recent IO-APIC changes made the bug show
> > up. To prevent this from happening, blacklist machines that are
> > known to be affected (nx6115 and 6715b in this particular case).
>
> Can you point to exactly _which_ recent change made it show up? I'd really
> like to know. _What_ was it that made us suddenly need this quirk when it
> wasn't necessary before? I'd like to understand the root cause here.
On my box it was caused by:
commit 691874fa96d6349a8b60f8ea9c2bae52ece79941
Author: Maciej W. Rozycki <macro@linux-mips.org>
Date: Tue May 27 21:19:51 2008 +0100
x86: I/O APIC: timer through 8259A second-chance
Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
and the whole story is described in this (huge) thread:
http://marc.info/?l=linux-kernel&m=121358440508410&w=4
> And how did you even start looking at that strange ACPI override?
Well, Matthew Garrett told us about that happening on the nx6125:
http://marc.info/?l=linux-kernel&m=121396307411930&w=4
and then Maciej analysed the breakage on the basis of a DSDT from the nx6325:
http://marc.info/?l=linux-kernel&m=121401068718826&w=4
As far as the Dmitry's and Jason's boxes are concerned, I recognized the
symptoms and asked them to verify that the blacklisting helped.
It appears that the buggy BIOS code has been copy-pasted to the entire range of
machines, for no good reason.
Thanks,
Rafael
next prev parent reply other threads:[~2008-10-06 17:11 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 18:36 2.6.27-rc8+ - first impressions Dmitry Torokhov
2008-10-05 18:59 ` Rafael J. Wysocki
2008-10-05 19:06 ` Dmitry Torokhov
2008-10-05 19:19 ` Rafael J. Wysocki
2008-10-05 19:27 ` Thomas Gleixner
2008-10-05 21:18 ` Dmitry Torokhov
2008-10-05 21:40 ` Parag Warudkar
2008-10-05 22:29 ` Rafael J. Wysocki
2008-10-06 6:23 ` Dmitry Torokhov
2008-10-06 9:59 ` [PATCH] x86 ACPI: Blacklist two HP machines with buggy BIOSes (Re: 2.6.27-rc8+ - first impressions) Rafael J. Wysocki
2008-10-06 14:54 ` Linus Torvalds
2008-10-06 15:00 ` Ingo Molnar
2008-10-06 17:17 ` Rafael J. Wysocki
2008-10-06 17:51 ` Maciej W. Rozycki
2008-10-06 17:54 ` Ingo Molnar
2008-10-06 20:59 ` Andi Kleen
2008-10-06 21:39 ` Maciej W. Rozycki
2008-10-06 22:11 ` [PATCH] x86: SB450: skip IRQ0 override if it is not routed to INT2 of IOAPIC Andreas Herrmann
2008-10-07 3:41 ` Ingo Molnar
2008-10-07 3:51 ` Dmitry Torokhov
2008-10-07 4:57 ` Ingo Molnar
2008-10-07 11:19 ` Dmitry Torokhov
2008-10-07 15:25 ` Maciej W. Rozycki
2008-10-07 20:31 ` Rafael J. Wysocki
2008-10-06 23:10 ` [PATCH] x86 ACPI: Blacklist two HP machines with buggy BIOSes (Re: 2.6.27-rc8+ - first impressions) Andi Kleen
2008-10-07 1:35 ` Maciej W. Rozycki
2008-10-07 4:42 ` Ingo Molnar
2008-10-07 5:38 ` Andi Kleen
2008-10-07 11:45 ` Matthew Garrett
2008-10-07 12:04 ` Ingo Molnar
2008-10-08 8:23 ` Peter Zijlstra
2008-10-06 17:15 ` Rafael J. Wysocki [this message]
2008-10-06 17:54 ` Maciej W. Rozycki
2008-10-05 19:10 ` 2.6.27-rc8+ - first impressions Arjan van de Ven
2008-10-06 6:28 ` Dmitry Torokhov
2008-10-06 19:53 ` Andreas Herrmann
2008-10-07 3:42 ` Dmitry Torokhov
2008-10-07 9:10 ` Andreas Herrmann
2008-10-07 11:37 ` Dmitry Torokhov
2008-10-07 12:07 ` Parag Warudkar
2008-10-08 1:07 ` Dmitry Torokhov
2008-10-07 13:19 ` Andreas Herrmann
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=200810061915.11936.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jason.vas.dias@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=torvalds@linux-foundation.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®