From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325 Date: Sun, 29 Jun 2008 16:00:27 +0200 Message-ID: <200806291600.29059.rjw@sisk.pl> References: <20080613232214.394fd6fd.sfr@canb.auug.org.au> <200806262152.02099.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from ogre.sisk.pl ([217.79.144.158]:44679 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755689AbYF2N6i (ORCPT ); Sun, 29 Jun 2008 09:58:38 -0400 In-Reply-To: Content-Disposition: inline Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: "Maciej W. Rozycki" Cc: Matthew Garrett , Ingo Molnar , Stephen Rothwell , linux-next@vger.kernel.org, LKML , Thomas Gleixner , ACPI Devel Maling List , Len Brown On Friday, 27 of June 2008, Maciej W. Rozycki wrote: > On Thu, 26 Jun 2008, Rafael J. Wysocki wrote: > > > Well, actually, I'm not sure that will work. I have only found > > acpi_skip_timer_override being set to 1 in two places, but it doesn't seem to > > be read anywhere. What am I missing? > > I believe I removed all the occurences. I am waiting for a proposal of a > quirk based on the DSDT ID -- my time is a bit too limited to study the > internals of our ACPI code at the moment; sorry about that. I will > complement it with a change to remove IRQ0 from I/O APIC tables as > promised then; this piece of code I am quite familiar with. Well, why don't we use the DMI identification as suggested by Matthew? I think we can safely assume that all of these boxes are broken for now and we can use a more fine grained identification in the future, if necessary. Thanks, Rafael