Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935512AbYGCHMt (ORCPT ); Thu, 3 Jul 2008 03:12:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754811AbYGCG63 (ORCPT ); Thu, 3 Jul 2008 02:58:29 -0400 Received: from idcmail-mo1so.shaw.ca ([24.71.223.10]:31648 "EHLO pd2mo2so.prod.shaw.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754875AbYGCFoP (ORCPT ); Thu, 3 Jul 2008 01:44:15 -0400 Date: Wed, 02 Jul 2008 23:44:09 -0600 From: Robert Hancock Subject: Re: [PATCH 2/2] acpi: Disable IRQ 0 through I/O APIC for some HP systems In-reply-to: To: "Maciej W. Rozycki" Cc: Ingo Molnar , Matthew Garrett , "Rafael J. Wysocki" , Len Brown , Thomas Gleixner , linux-next@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Message-id: <486C6729.4020903@shaw.ca> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1520 Lines: 30 Maciej W. Rozycki wrote: > From: Matthew Garrett > > 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/