From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 21 22:39:22 2008 Return-Path: Delivered-To: acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A86DD16A417 for ; Mon, 21 Jan 2008 22:39:22 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 665E713C468 for ; Mon, 21 Jan 2008 22:39:22 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.2/8.14.2/NETPLEX) with ESMTP id m0LMdLXY017277; Mon, 21 Jan 2008 17:39:21 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Mon, 21 Jan 2008 17:39:21 -0500 (EST) Date: Mon, 21 Jan 2008 17:39:21 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: "Alexandre \"Sunny\" Kovalenko" In-Reply-To: Message-ID: References: <1200369199.2054.38.camel@RabbitsDen> <1200844521.33164.18.camel@RabbitsDen> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: acpi@freebsd.org Subject: Re: How to disable acpi thermal? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2008 22:39:22 -0000 On Mon, 21 Jan 2008, Daniel Eischen wrote: > On Sun, 20 Jan 2008, Alexandre "Sunny" Kovalenko wrote: > >> >> On Tue, 2008-01-15 at 15:34 -0500, Daniel Eischen wrote: >>> [ Redirected from -current ] >>> >>> >>> I posted the acpidump here: >>> >>> http://people.freebsd.org/~deischen/stl2.iasl >>> >>> The problem is that acpi_thermal keeps shutting down the system >>> after 2 minutes into a buildkernel. The system has no load other >>> than the buildkernel at the time it shuts down. >>> >>> The system is a Intel STL2 Tupelo motherboard with 1 CPU, the >>> other CPU socket being occupied by a CPU terminator thingy. >>> I uncovered the rackmount system and watched it while building >>> a kernel. With the cover off the acpi monitored temperature >>> went to 107C and stayed there. It only took a minute or two >>> to get there. I felt around inside the chassis and nothing >>> was even near being to warm or hot. With the cover on, the >>> temperature goes to 111/112C before being shutdown by acpi_thermal >>> (the limit being 110C). There is no way anything in that >>> chassis is anywhere near 100C. I've disabled acpi_thermal >>> for now, but it'd be nice to get a better fix. >>> >>> Any ideas? >>> >> Firstly, sorry for the delay in answer -- daytime job decided to kick in >> with the vengeance. >> >> I took a look at the ASL and it does seem that this thing has embedded >> controller and that is where _TMP method gets its temperature reading >> from (this being conditional on the CPU present in the socket -- >> otherwise you get 5 degrees Celsius, hardcoded in the ASL). >> >> So the questions are: >> >> -- does temperature in TZ2 grow over time as well? (TZ1 should stay at >> 5C all the time). > > No, it stays around the same. I saw it go to 38 from 35 in > the same time that TZ0 went to over 110C. I didn't see it > get any higher than that. One additional note, this is a dual CPU system with only one CPU in it, and I am not running an SMP kernel. I was looking at the iasl, and noticed this for TZ0: ThermalZone (TZC0) { Method (_TMP, 0, NotSerialized) { --> If (LNotEqual (And (\_SB.NCPU, 0x01), 0x01)) { Return (\_SB.PCI0.ISA0.EC0.TC2K (0x05)) } Else { Store (\_SB.PCI0.ISA0.EC0.EGTV (0x21, 0x00), TZT0) If (LEqual (TZT0, CTC0)) { Add (TZT0, 0x0A, TZT0) } Return (TZT0) } } Is it possible that my configuration with only one CPU is confusing things? -- DE