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 16:35:22 +0100 Message-ID: <20080630153522.GA26185@srcf.ucam.org> References: <20080613232214.394fd6fd.sfr@canb.auug.org.au> <200806292123.16237.rjw@sisk.pl> <200806300056.16399.rjw@sisk.pl> <20080630090607.GA18856@srcf.ucam.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org To: "Maciej W. Rozycki" Cc: "Rafael J. Wysocki" , Ingo Molnar , Stephen Rothwell , linux-next@vger.kernel.org, LKML , Thomas Gleixner , ACPI Devel Maling List , Len Brown , Andi Kleen , Andrew Morton , Linus Torvalds List-Id: linux-next.vger.kernel.org On Mon, Jun 30, 2008 at 04:29:33PM +0100, Maciej W. Rozycki wrote: > Now I did a search of the Internet and have become puzzled. Apparently > there *are* other devices using this DSDT. See for example a thread at: > "http://bbs.archlinux.org/viewtopic.php?pid=359559" where an owner of an > HP Compaq 6715s has some other problems with a DSDT which coincidentally > is the very same HP/SB400/10000 (though built with a different ASL > compiler, hmm...). Hm. It'd be interesting to know whether the bizarre debug code is in there. What's even more interesting is that the 6715s is an SB600, not an SB400... > Matthew, where did you get these DMI IDs from? -- I cannot see them being > reported in any bootstrap log. dmidecode or /sys/class/dmi. They're not reported on boot. -- Matthew Garrett | mjg59@srcf.ucam.org