From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
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 14:04:28 +0200 [thread overview]
Message-ID: <20081007120428.GA4392@elte.hu> (raw)
In-Reply-To: <20081007053808.GB20740@one.firstfloor.org>
* Andi Kleen <andi@firstfloor.org> wrote:
> On Tue, Oct 07, 2008 at 02:35:01AM +0100, Maciej W. Rozycki wrote:
> >
> > > > 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")
> >
> > I am happy to fix any bugs I introduced myself (as much as one can
> > be happy about mistakes once they have discovered they made them
> > that is) and certainly have a look into other Linux bugs by request
> > of any vendor of a Linux distribution made on behalf of a hardware
> > manufacturer.
> >
> > OTOH I do not feel responsible even a little bit for someone else's
> > bugs like those of BIOS developers. Though I will certainly
> > consider providing them with any assistance needed to get things
> > related to Linux resolved in a best possible way if they ask nicely.
>
> To be honest I think you have a unrealistic approach to this. That is
> not how it works.
>
> For the BIOS developers OS are like some piece of random hardware ot a
> OS developer. If something doesn't work and if they care they will add
> a workaround. Just as the OS developer adds a workaround for the
> hardware issue. And yes workarounds are typically not pretty. And
> sometimes the workaround come later back to bite someone That is what
> happened here. But they still have to support the old releases if they
> worked before, otherwise they got a regression too.
>
> Using a PCI ID quirk to disable the workaround is a reasonable
> approach, although it has its issues too.
>
> Also calling the workaround a BIOS bug is just unfair in this case. It
> really isn't.
The BIOS causes all thermal trip points to be 16C when the kernel pokes
the IO-APIC pins, causing the system to be very slow and causing the CPU
fan to spin like mad. That is utterly broken. So stop wasting our time
with your stupid nonsense.
Ingo
next prev parent reply other threads:[~2008-10-07 12: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 ` [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 [this message]
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=20081007120428.GA4392@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.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=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;
as well as URLs for NNTP newsgroup(s).