From owner-freebsd-questions@FreeBSD.ORG Mon Aug 5 05:05:19 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2D46570C for ; Mon, 5 Aug 2013 05:05:19 +0000 (UTC) (envelope-from vagabond@blackfoot.net) Received: from nightmare.dreamchaser.org (nightmare.dreamchaser.org [12.32.44.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F27B12839 for ; Mon, 5 Aug 2013 05:05:18 +0000 (UTC) Received: from breakaway.dreamchaser.org (breakaway.dreamchaser.org. [12.32.36.73]) by nightmare.dreamchaser.org (8.13.6/8.13.6) with ESMTP id r75552OV014320; Sun, 4 Aug 2013 23:05:03 -0600 (MDT) (envelope-from vagabond@blackfoot.net) Message-ID: <51FF327E.6000002@blackfoot.net> Date: Sun, 04 Aug 2013 23:05:02 -0600 From: Gary Aitken User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130730 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: AMD Phenom II X4 temperature issues (was Re: hardware monitor) References: <51FEBE38.2000202@blackfoot.net> <20130804231548.dbb1fd2e.freebsd@edvax.de> <51FEE23D.3020402@blackfoot.net> <51FEE3E0.5080709@blackfoot.net> <51FEF20B.2090503@fjl.co.uk> <51FF0780.1010908@blackfoot.net> <51FF1E69.4050401@fjl.co.uk> In-Reply-To: <51FF1E69.4050401@fjl.co.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (nightmare.dreamchaser.org [12.32.36.65]); Sun, 04 Aug 2013 23:05:03 -0600 (MDT) Cc: freebsd-doc@fjl.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 05:05:19 -0000 On 08/04/13 21:39, Frank Leonhardt wrote: > On 05/08/2013 03:01, Gary Aitken wrote: >>> 50C isn't crazy. >> Actually, the 50C figure is just where it shoots to for starters. >> Mfg specs say 62C max, so I stall the process when it gets around >> 59 and still climbing steeply. > > The manufactures specs I found when I looked that range of CPUs up > was 71C > > http://www.amd.com/us/products/desktop/processors/phenom-ii/Pages/phenom-ii-model-number-comparison.aspx > > But there could be two figures - one for maximum desirable working > and one for maximum "or else". Maybe; although the number I quoted wasn't from AMD, and the two I just found at amd both said 71. >>> Did you get anywhere with the ACPI suggestion Try >>> hw.acpi.thermal.tz0.active=1 to make the fan come on and stay on >>> (tz0 or as appropriate). >> The fan is on and stays on all the time at the moment... > > It it full speed all the time? I really don't know what full speed on the fan is / feels like / sounds like. It's pretty quiet and there's a noisy old system nearby... xmbmon doesn't show fan speeds, nor does amdtemp provide access to them. Is there some other kernel module for fan speeds? >>> Here's the fun part. Is your system doing a thermal overload >>> shutdown? >> There is no indication in messages; the last thing before it shut >> down the last time was some su's and root logins. > > This suggests it's not the ACPI in FreeBSD shutting you down, but > something on the motherboard. That was my guess as well. >>> it might help if you posted the results of "sysctl >>> hw.acpi.thermal", but in the mean time look at: >>> >>> hw.acpi.thermal.tz0._HOT hw.acpi.thermal.tz0._CRT >>> >> I don't see any of those; here's what shows up in sysctl -a : >> >> hw.acpi.supported_sleep_state: S1 S3 S4 S5 >> hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 >> hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 >> hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 >> hw.acpi.verbose: 0 hw.acpi.disable_on_reboot: 0 >> hw.acpi.handle_reboot: 0 hw.acpi.reset_video: 0 >> hw.acpi.cpu.cx_lowest: C1 > > Yep - definitely suggests that the thermal control isn't being done > by FreeBSD! ok, but how do I get it in there if I want it? > Go no further on this route, but check the > motherboard/BIOS. I had one machine shut itself down due to a faulty > thermistor (raise the threshold/ignore) but it normally happens when > the parameters are wrong or the fan has failed. As your fan hasn't > failed and the reported temperature is believable my best guesses are > that the BIOS is either picking the wrong shutdown temperature for > the CPU or your air ducting isn't good enough and it really is > getting too hot. Is there a chance that the BIOS pre-dates the CPU > and just doesn't know its working parameters, and is therefore > playing safe? I'll check the BIOS next time I reboot. Air ducting shouldn't be a problem; I've got the side of the case off... > Incidentally, ACPI is an Intel specification but applies AMD64 CPUs > too. The thermal module only works on some chip-sets. FWIW I've found > it works on more AMD platforms than it does Intel ones. > > Regards, Frank.