Date: Mon, 21 Jan 2008 15:44:43 -0500 (EST) From: Daniel Eischen <deischen@freebsd.org> 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.0801211510290.805@sea.ntplx.net> In-Reply-To: <1200844521.33164.18.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> <1200844521.33164.18.camel@RabbitsDen>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > -- do you see AE_NO_HARDWARE_RESPONSE messages, and if yes, could you > try to increase debug.acpi.ec.timeout -- I think (sm) it is in ms and > default is 750. No, I don't get any of those messages. > -- do you have ACPI_DEBUG option in your kernel? If not, could you, > maybe, build kernel with that, and turn on full debug, let temperature > climb for a while and send me debug output. I did this with: debug.acpi.level: ACPI_LV_ERROR ACPI_LV_WARN ACPI_LV_INIT ACPI_LV_DEBUG_OBJECT ACPI_LV_INFO ACPI_LV_ALL_EXCEPTIONS debug.acpi.layer: ACPI_UTILITIES ACPI_HARDWARE ACPI_EVENTS ACPI_TABLES ACPI_NAMESPACE ACPI_PARSER ACPI_DISPATCHER ACPI_EXECUTER ACPI_RESOURCES ACPI_CA_DEBUGGER ACPI_OS_SERVICES ACPI_CA_DISASSEMBLER ACPI_ALL_COMPONENTS ACPI_THERMAL This was with settings debug.acpi.level="ACPI_LV_ALL_EXCEPTIONS" and debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_THERMAL". I tried debug.acpi.level="ACPI_LV_VERBOSITY3 ACPI_LV_VERBOSE" but it made the system unusable (hung). The messages I get are basicall the same thing over and over, posted here: http://people.freebsd.org/~deischen/acpi.debug.012108 I do see this a lot: dsobject-0491 [2238] DsBuildInternalPackage: Package List length larger than NumElements count (2), truncated The beginning of the log is with tz0 temperature at around 44C (just before the 'sudo make -DNO_CLEAN -DNO_CLEANDIR buildworld', also caught in the log). The end of the log, about 2 minutes later, tz0 temperature is 113C. tz2 temperature was 36C and 38C respectively. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0801211510290.805>