linux-kernel - Re: [PATCH 2/2] acpi: Disable IRQ 0 through I/O APIC for some HP systems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-id: <486C6729.4020903@shaw.ca>
Date:	Wed, 02 Jul 2008 23:44:09 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	"Maciej W. Rozycki" <macro@...ux-mips.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Matthew Garrett <mjg59@...f.ucam.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, Len Brown <lenb@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-next@...r.kernel.org, linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] acpi: Disable IRQ 0 through I/O APIC for some HP
 systems

Maciej W. Rozycki wrote:
> From: Matthew Garrett <mjg59@...f.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..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/