Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753653AbXLIWm2 (ORCPT ); Sun, 9 Dec 2007 17:42:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751075AbXLIWmT (ORCPT ); Sun, 9 Dec 2007 17:42:19 -0500 Received: from smtp-100-sunday.nerim.net ([62.4.16.100]:54541 "EHLO kraid.nerim.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750767AbXLIWmT (ORCPT ); Sun, 9 Dec 2007 17:42:19 -0500 Date: Sun, 9 Dec 2007 23:42:15 +0100 From: Jean Delvare To: Elvis Pranskevichus Cc: Mike Houston , Adrian Bunk , mhoffman@lightlink.com, linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org, Bjorn Helgaas , Adam Belay Subject: Re: [lm-sensors] 2.6.24-rc4 hwmon it87 probe fails Message-ID: <20071209234215.748ed407@hyperion.delvare> In-Reply-To: References: <20071204215154.7f26285e.mikeserv@bmts.com> <20071209000554.GF20441@stusta.de> <20071208212234.e00b74cd.mikeserv@bmts.com> <20071209105028.06ed52a6@hyperion.delvare> X-Mailer: Sylpheed-Claws 2.5.5 (GTK+ 2.10.6; x86_64-suse-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1405 Lines: 42 Hi Elvis, On Sun, 09 Dec 2007 16:12:25 -0500, Elvis Pranskevichus wrote: > I have exactly the same problem here on a Gigabyte GA-965G-DS3 motherboard > based box: Same motherboard as Mike has. > it87: Found IT8718F chip at 0x290, revision 1 > it87: in3 is VCC (+5V) > it87 it87.656: Failed to request region 0x290-0x297 > it87: probe of it87.656 failed with error -16 > > git bisecting revealed the offending commit: > > a7839e960675b54: PNP: increase the maximum number of resources > > Happened between rc3 and rc4. > > > Either way, the overlapping areas smell like a BIOS bug, meaning that > > you should look for an updated BIOS for your system first. > > > >> http://www.mikeserv.com/temp/config-2.6.24-rc4.txt > > > > This indeed looks like a broken ACPI BIOS since the aforementioned commit > touches only the PNP ACPI driver. I'm not sure how to work around this, > though. Ideas? Complaining to Gigabyte seems to be the best approach. In the meantime, I guess that booting with pnpacpi=off should fix your problem. But it might break something else; I'm not sure what the PNP ACPI driver is good for in the first place. -- Jean Delvare -- 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/