From: Ingo Molnar <mingo@elte.hu>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: 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: Mon, 6 Oct 2008 19:54:56 +0200 [thread overview]
Message-ID: <20081006175456.GA24480@elte.hu> (raw)
In-Reply-To: <alpine.LFD.1.10.0810061815060.10470@ftp.linux-mips.org>
* Maciej W. Rozycki <macro@linux-mips.org> wrote:
> On Mon, 6 Oct 2008, Ingo Molnar wrote:
>
> > i think it was caused by this stream of IO-APIC changes:
> >
> > 49a66a0: x86: I/O APIC: Always report how the timer has been set up
> > 17c4469: x86: I/O APIC: Include <asm/i8259.h> required by some code
> > 593f4a7: x86: APIC: remove apic_write_around(); use alternatives
> > ce8b06b: x86: I/O APIC: remove an IRQ2-mask hack
> > af17478: x86: I/O APIC: Never configure IRQ2
> > c88ac1d: x86: L-APIC: Always fully configure IRQ0
> > 1baea6e: x86: L-APIC: Set IRQ0 as edge-triggered
> >
> > Rafael/Maciej, which of these is causing it? ce8b06b ("x86: I/O APIC:
> > remove an IRQ2-mask hack")?
>
> None of the above. This:
>
> 691874f: x86: I/O APIC: timer through 8259A second-chance
>
> This change has fixed a problem with the timer for a lot of systems
> and permitted the removal of a bunch of horrible hacks we used to have
> in our I/O-APIC/timer code, including a command-line override
> parameter, needed so that some systems would boot at all.
>
> This single instance of a piece of some HP gear being twisted beyond
> belief is IMO a minor annoyance and price to pay compared to the gain.
> Please note that apart from the DSDT being buggy on this machine, it
> has an incorrect IRQ 0 override in the ACPI table pointing to the pin
> #2 of the I/O APIC, which is in fact routed to the output of the
> master 8259A. Additionally the pin #0 of the I/O APIC which is indeed
> routed to the output of the 8254 does not receive any interrupts,
> presumably because of some misconfiguration during BIOS
> initialisation. So in fact this machine suffers from three
> configuration problems at once of which all add up to the end result
> we can observe.
okay. Perhaps we can find some better DMI filter for affected
HP+AMD+Turion laptops - how futile that might be. No chance to have some
automated non-DMI check?
Ingo
next prev parent reply other threads:[~2008-10-06 17:55 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 [this message]
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
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=20081006175456.GA24480@elte.hu \
--to=mingo@elte.hu \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.