From: Robert Hancock <hancockr@shaw.ca>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Matthew Garrett <mjg59@srcf.ucam.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Len Brown <lenb@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-next@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] acpi: Disable IRQ 0 through I/O APIC for some HP systems
Date: Wed, 02 Jul 2008 23:44:09 -0600 [thread overview]
Message-ID: <486C6729.4020903@shaw.ca> (raw)
In-Reply-To: <fa.OuKI5CNmq3HqeBQCfWOUtrq4+oA@ifi.uio.no>
Maciej W. Rozycki wrote:
> From: Matthew Garrett <mjg59@srcf.ucam.org>
>
> Some HP laptops have a problem with their DSDT reporting as
> HP/SB400/10000, which includes some code which overrides all temperature
> trip points to 16C if the INTIN2 input of the I/O APIC is enabled. This
> input is incorrectly designated the ISA IRQ 0 via an interrupt source
> override even though it is wired to the output of the master 8259A and
> INTIN0 is not connected at all. So far two models have been identified,
> namely nx6125 and nx6325.
>
> Use a knob provided by the I/O APIC interrupt registration code to
> abandon any attempts to route IRQ 0 through the I/O APIC for these
> systems.
Just a thought.. has anyone recently looked into using the RTC timer
instead of the PIT as the default clockevent source? There still seem to
be systems like these seeping through with broken PIT through IOAPIC
since Windows apparently doesn't use that config at all. If we could use
the RTC instead (which is apparently what Windows does) we could avoid
that problem.
The last I read on the subject, the issue was that the RTC timer
frequencies didn't match the existing Linux HZ values, but I'm not sure
if that's still an issue with the current clockevents infrastructure..
next parent reply other threads:[~2008-07-03 5:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.OuKI5CNmq3HqeBQCfWOUtrq4+oA@ifi.uio.no>
2008-07-03 5:44 ` Robert Hancock [this message]
2008-07-01 0:12 [PATCH 2/2] acpi: Disable IRQ 0 through I/O APIC for some HP systems Maciej W. Rozycki
2008-07-01 0:17 ` Matthew Garrett
2008-07-01 8:46 ` Ingo Molnar
2008-07-01 19:58 ` Rafael J. Wysocki
2008-07-01 20:24 ` Ingo Molnar
2008-07-04 21:21 ` Rafael J. Wysocki
2008-07-06 23:02 ` Rafael J. Wysocki
2008-07-07 1:19 ` Rafael J. Wysocki
2008-07-07 7:17 ` Ingo Molnar
2008-07-07 7:36 ` Ingo Molnar
2008-07-07 12:24 ` Rafael J. Wysocki
2008-07-07 11:41 ` Maciej W. Rozycki
2008-07-07 12:23 ` Rafael J. Wysocki
2008-07-07 14:01 ` Maciej W. Rozycki
2008-07-07 18:03 ` Rafael J. Wysocki
2008-07-07 20:10 ` Maciej W. Rozycki
2008-07-07 20:31 ` Rafael J. Wysocki
2008-07-07 21:39 ` Maciej W. Rozycki
2008-07-07 22:10 ` Rafael J. Wysocki
2008-07-07 12:28 ` Rafael J. Wysocki
2008-07-07 17:10 ` Maciej W. Rozycki
2008-07-07 17:51 ` Ray Lee
2008-07-07 18:09 ` Rafael J. Wysocki
2008-07-07 19:59 ` Maciej W. Rozycki
2008-07-07 20:17 ` Rafael J. Wysocki
2008-07-07 21:38 ` Maciej W. Rozycki
2008-07-07 20:30 ` Maciej W. Rozycki
2008-07-07 3:54 ` Zhao Forrest
2008-07-07 12:34 ` Rafael J. Wysocki
2008-07-08 11:24 ` Andreas Herrmann
2008-07-08 14:39 ` Maciej W. Rozycki
2008-07-08 15:27 ` Rafael J. Wysocki
2008-07-08 16:25 ` Maciej W. Rozycki
2008-07-08 16:54 ` Rafael J. Wysocki
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=486C6729.4020903@shaw.ca \
--to=hancockr@shaw.ca \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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).