From: Andi Kleen <andi@firstfloor.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Len Brown <lenb@kernel.org>,
Jason Vas Dias <jason.vas.dias@gmail.com>
Subject: Re: [PATCH] x86 ACPI: Blacklist two HP machines with buggy BIOSes (Re: 2.6.27-rc8+ - first impressions)
Date: Tue, 7 Oct 2008 01:10:02 +0200 [thread overview]
Message-ID: <20081006231002.GN3180@one.firstfloor.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0810062227100.10470@ftp.linux-mips.org>
On Mon, Oct 06, 2008 at 10:39:25PM +0100, Maciej W. Rozycki wrote:
> On Mon, 6 Oct 2008, Andi Kleen wrote:
>
> > The real reason is actually a workaround in the BIOS for problems
> > in the older Linux code that caused duplicated timer interrupts. The
> > old Linux would fall into "enable both IO-APIC and 8259" fallback mode
> > and the resulted in duplicated timer events, which made everything unhappy.
> > They instead configured the northbridge in a way that one of the inputs
> > is ignored.
>
> Hmm, working around Linux problems in the BIOS is a new and truly odd
> concept to me.
Except perhaps for the cheapest consumer parts and many laptops Linux is
definitely on the radar now for many BIOS developers.
> It's not that we are unresponsive or do not take
> responsibility for our bugs, is it?
These workarounds are not for mainline kernels but for specific
distribution releases (as in "fixes SLES/RHEL x.y" instead of
"fixes 2.6.xy")
Even when the distributors update their kernels the old releases
do not go away are still used and the workarounds get in.
> > You won't be able to DMI list it, that workaround is widely used
> > in lots of different systems.
>
> Well, perhaps, but the thermal trip point phenomenon seems unique to this
> family of systems. The other aspects of the problem do not really matter
> anymore as we seem to have addressed them robustly enough now.
When you need DMI entries you clearly haven't.
-Andi
next prev parent reply other threads:[~2008-10-06 23:04 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 ` Andi Kleen [this message]
2008-10-07 1:35 ` [PATCH] x86 ACPI: Blacklist two HP machines with buggy BIOSes (Re: 2.6.27-rc8+ - first impressions) 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
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=20081006231002.GN3180@one.firstfloor.org \
--to=andi@firstfloor.org \
--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=rjw@sisk.pl \
--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
Powered by JetHome