From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325 Date: Mon, 30 Jun 2008 01:47:11 +0100 Message-ID: <20080630004711.GA14118@srcf.ucam.org> References: <20080613232214.394fd6fd.sfr@canb.auug.org.au> <20080629200210.GB31633@elte.hu> <200806300106.38414.rjw@sisk.pl> <20080630004544.GB19093@one.firstfloor.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([93.93.128.6]:47460 "EHLO vavatch.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751386AbYF3ArT (ORCPT ); Sun, 29 Jun 2008 20:47:19 -0400 Content-Disposition: inline In-Reply-To: <20080630004544.GB19093@one.firstfloor.org> Sender: linux-next-owner@vger.kernel.org List-ID: To: Andi Kleen Cc: "Rafael J. Wysocki" , "Maciej W. Rozycki" , Ingo Molnar , Stephen Rothwell , linux-next@vger.kernel.org, LKML , Thomas Gleixner , ACPI Devel Maling List , Len Brown , Andi Kleen , Andrew Morton , Linus Torvalds On Mon, Jun 30, 2008 at 02:45:44AM +0200, Andi Kleen wrote: > ... also past experience is that DMI tables don't work well for this. > We tried that early when ACPI was still very problematic and it turned > out to be a flawed non-scalable strategy, > > Typically the configurations causing problems are in multiple motherboards > with different DMI strings and it's very difficult to catch them all. > > Also sometimes BIOS behaviour changes over versions and that's tricky to catch > with the standard DMI matches. In this specific case, the problem is clearly due to nonsensical code in the DSDT that alters the thermal trip points based on ioapic configuration. It's only been observed on two almost identical models from one manufacturer, and doesn't occur on any other known machines with the same chipset. I think it's safe to special-case. -- Matthew Garrett | mjg59@srcf.ucam.org