Date: Wed, 20 Feb 2008 17:15:45 -0500 (EST) From: Daniel Eischen <eischen@vigrid.com> To: "Alexandre \"Sunny\" Kovalenko" <alex.kovalenko@verizon.net> Cc: acpi@freebsd.org Subject: Re: How to disable acpi thermal? Message-ID: <Pine.GSO.4.64.0802201711090.7855@sea.ntplx.net> In-Reply-To: <1203131179.833.32.camel@RabbitsDen> References: <Pine.GSO.4.64.0801142156360.24324@sea.ntplx.net> <1200369199.2054.38.camel@RabbitsDen> <Pine.GSO.4.64.0801151525160.29868@sea.ntplx.net> <1203131179.833.32.camel@RabbitsDen>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 15 Feb 2008, Alexandre "Sunny" Kovalenko wrote: > > On Tue, 2008-01-15 at 15:34 -0500, Daniel Eischen wrote: >> [ Redirected from -current ] >> >> On Mon, 14 Jan 2008, Alexandre "Sunny" Kovalenko wrote: >> >>> >>> On Mon, 2008-01-14 at 21:56 -0500, Daniel Eischen wrote: >>>> >>>> Thermal zone 0 skyrockets past 110C in a couple of minutes >>>> when trying to build a kernel. All the other zones stay >>>> relatively static. I suspect something is wrong somewhere >>>> because this machine is very lightly loaded and has never >>>> had a problem until now. I just upgraded it from 4.x to >>>> 7.0. >>> >>> It need not to be bogus -- if I turn off fan on my ThinkPad it will >>> overheat and shut itself down within couple of minutes of buildworld, >>> starting from the relative cool state. From the look of the stuff below >>> your fan should kick in no later then 10 seconds after tz0 reached 77C. >>> Do you hear it running before shutdown? If yes, maybe lowering threshold >>> in AC0 down from 77C will help. If not -- you will need to figure out >>> who is supposed to turn on the fan. You can dump your ASL (instructions >>> in the handbook) and post it someplace accessible -- I will take a look >>> and maybe spot something interesting, but, being far from the expert in >>> the field, I do not promise too much. >> >> 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? >> > You can try this patch on your ASL, which might just cause passive > cooling to kick in. If you decide to try a patch, I would like to see > the output of I guess I'm confused - how can passive cooling "kick in". Isn't passive cooling always on if you are using a heatsink? > sysctl hw.acpi.thermal > > regardless of the outcome. > > OTOH, it just occurred to me that I have observed something like that on > my previous laptop. I used cheap thermal paste between the CPU and the > heatsink and I used a lot of it. Chassis were relatively cool and yet > CPU sensor hit critical trip point. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0802201711090.7855>