From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [lm-sensors] Could the k8temp driver be interfering with ACPI? Date: Fri, 2 Mar 2007 11:47:47 +0000 Message-ID: <20070302114747.GB1212@srcf.ucam.org> References: <45D5EA88.7090300@redhat.com> <45D6DDCE.5050803@assembler.cz> <45D7461A.2040808@redhat.com> <20070218183805.5a4fd813.khali@linux-fr.org> <20070228213803.GA4877@ucw.cz> <20070301152655.f232db64.khali@linux-fr.org> <20070302114023.GD2163@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([217.147.92.49]:35001 "EHLO vavatch.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422831AbXCBLsM (ORCPT ); Fri, 2 Mar 2007 06:48:12 -0500 Content-Disposition: inline In-Reply-To: <20070302114023.GD2163@elf.ucw.cz> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Pavel Machek Cc: Jean Delvare , Chuck Ebbert , Rudolf Marek , linux-acpi@vger.kernel.org, linux-kernel , lm-sensors@lm-sensors.org On Fri, Mar 02, 2007 at 12:40:23PM +0100, Pavel Machek wrote: > Whitelist seems like a way to go :(. The DSDT code clearly can't touch the hardware itself - hardware access is carried out by the kernel. If we can identify cases where ACPI reads and writes would touch resources claimed by other drivers, that would be a good starting point for working out what's going on. Of course, this ignores the case where the DSDT just traps into SMM code. That one is clearly unsolvable. -- Matthew Garrett | mjg59@srcf.ucam.org From mboxrd@z Thu Jan 1 00:00:00 1970 From: mjg59@srcf.ucam.org (Matthew Garrett) Date: Fri, 02 Mar 2007 11:47:47 +0000 Subject: [lm-sensors] Could the k8temp driver be interfering with ACPI? Message-Id: <20070302114747.GB1212@srcf.ucam.org> List-Id: References: <45D5EA88.7090300@redhat.com> <45D6DDCE.5050803@assembler.cz> <45D7461A.2040808@redhat.com> <20070218183805.5a4fd813.khali@linux-fr.org> <20070228213803.GA4877@ucw.cz> <20070301152655.f232db64.khali@linux-fr.org> <20070302114023.GD2163@elf.ucw.cz> In-Reply-To: <20070302114023.GD2163@elf.ucw.cz> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Pavel Machek Cc: Jean Delvare , Chuck Ebbert , Rudolf Marek , linux-acpi@vger.kernel.org, linux-kernel , lm-sensors@lm-sensors.org On Fri, Mar 02, 2007 at 12:40:23PM +0100, Pavel Machek wrote: > Whitelist seems like a way to go :(. The DSDT code clearly can't touch the hardware itself - hardware access is carried out by the kernel. If we can identify cases where ACPI reads and writes would touch resources claimed by other drivers, that would be a good starting point for working out what's going on. Of course, this ignores the case where the DSDT just traps into SMM code. That one is clearly unsolvable. -- Matthew Garrett | mjg59 at srcf.ucam.org