From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 22 02:51:45 2013 Return-Path: Delivered-To: freebsd-acpi@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 ESMTPS id 71AF9384 for ; Sun, 22 Dec 2013 02:51:45 +0000 (UTC) Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0620E1653 for ; Sun, 22 Dec 2013 02:51:44 +0000 (UTC) Received: by mail-we0-f177.google.com with SMTP id u56so3818195wes.22 for ; Sat, 21 Dec 2013 18:51:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Hrm/Txh82n5B73akzlG/5xso1QU/B06hnRkuNExrre0=; b=q1diH7fZGZgJTGZ9AGsFAolAT2qYRgWfUkmqoNDixNY/4ZW3R3YlrsJgz9dqnOtYsV mOfbM/svl/VTK1Q9vw+20o0GQwf37cCPS+3q7FfHxHS3TsMc5Em8+Q3Gs9xvcoyI3h7f b6b4kGXApowJxtH0dC59lpjzcsVkHhSqTBIjLJHT+0pie5QlLF62/Gv2JaOKBCCpDJ3W lMCbivExaYrBDfb2tJFh8oDGC/jDpJj5e5Dr9id5+8vMZk4z4bY/ys447nADKOIjH2T2 eEZ0qLl/7NFeypN9TZMA7wCf9v2udxIRzXyYHAT8qbYt85vgSYk0M1Cc1vFSPuKeaGhW fNCA== X-Received: by 10.180.79.67 with SMTP id h3mr13211059wix.58.1387680702362; Sat, 21 Dec 2013 18:51:42 -0800 (PST) Received: from ketas-laptop.mydomain (ketas-laptop6.si.pri.ee. [2001:ad0:91f:0:21a:6bff:fe66:2ad3]) by mx.google.com with ESMTPSA id c1sm6231617wje.4.2013.12.21.18.51.37 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 21 Dec 2013 18:51:41 -0800 (PST) Sender: Sulev-Madis Silber Message-ID: <52B653AD.7090705@hot.ee> Date: Sun, 22 Dec 2013 04:51:25 +0200 From: Sulev-Madis Silber User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: ito Subject: Re: loud fan pavilion ze2000 References: <1387551635.2533.21.camel@res-cmts> <20131221152703.E25305@sola.nimnet.asn.au> <1387666895.5356.22.camel@res-cmts> In-Reply-To: <1387666895.5356.22.camel@res-cmts> X-TagToolbar-Keys: D20131222045125629 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org, Ian Smith X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Dec 2013 02:51:45 -0000 No, that's a disk filler :) Also useful sometimes... For CPU load test one needs "dd if=/dev/urandom of=/dev/null" (might want to run it hw.ncpu times to cover all). Just watch out, dd is one of those tools which can easily bring disaster into house. On 2013-12-22 01:01, ito wrote: > PS, is this the exact command? > " dd if=/dev/random > of=/dev/null " From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 22 05:52:06 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8CEF1574 for ; Sun, 22 Dec 2013 05:52:06 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D7BF7120A for ; Sun, 22 Dec 2013 05:52:05 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id rBM5pujO081237; Sun, 22 Dec 2013 16:51:56 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sun, 22 Dec 2013 16:51:56 +1100 (EST) From: Ian Smith To: ito Subject: Re: loud fan pavilion ze2000 In-Reply-To: <1387666895.5356.22.camel@res-cmts> Message-ID: <20131222153537.T25305@sola.nimnet.asn.au> References: <1387551635.2533.21.camel@res-cmts> <20131221152703.E25305@sola.nimnet.asn.au> <1387666895.5356.22.camel@res-cmts> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Dec 2013 05:52:06 -0000 On Sat, 21 Dec 2013 18:01:35 -0500, ito wrote: > Hello Ian, > > At 50 through 62C the dev.cpu.0.freq: 1298 > > at 70C , 1135 > > back up to 1298 Right, 1135 / 1298 ~= .875 = 7/8, so yes that's your 1.3GHz CPU dropping down one step for thermal control. > dev.cpu.0.freq_levels: 1298/-1 1298/-1 973/-1 811/-1 > 649/-1 486/-1 324/-1 162/-1 > > Also directly below that: > > dev.p4tcc.0.freq_settings: 10000/-1 8750/-1 7500/-1 6250/-1 5000/-1 > 3750/-1 2500/-1 1250/-1 > > I suppose that is the 8 (freq_levels) you where referring to. Further I > infer that this -1 means that the BIOS has set them or does set them. Yes, but here the -1 indicates for freq_levels that power consumption in milliwatts at that freq is unknown, likely the same for p4tcc settings. > I set hw.acpi.thermal.tz0._PSV: 70C > > Trying "find / acpi" to see it work. > > While doing the above (find) the fan is on but not full out. find(1) works disk harder than CPU as a rule, though here that command gets xorg about 70% busy, and keeps going for ages after hitting ^C, as it lists each file on the disk :) Maybe useful: find / -name "*acpi*" >From below: > PS, is this the exact command? > " dd if=/dev/random > of=/dev/null " No, no. I was careful to be precise, and yes a mistyped dd can be dangerous, and redirected to a file could indeed fill your disk. Fortunately that one doesn't work, invalid filename. see dd(1). > I am reluctant to type anything like dd: anything: I'm not really that > confident with the command line. Without your redirection it just reads from /dev/random, burning CPU, discarding the output, until you hit ^C .. perfectly safe. > After setting the PSV value it does not go above 71 when rendering > animation with blender. Yeah rendering will busy the CPU (and GPU too) pretty well. Good, so we know passive cooling works (in case your fan ever really packs up). > I will try cleaning it again, but I think I remember that I thought > cleaning would fix it before. Unless you live in an extraordinarily dust-free environment, this needs doing with some regularity anyway. I did mine the other day, as summer ambient temperatures over 30C are becoming normal here (happy solstice!) At the temperatures you've quoted, apart from annoying fan noise, it doesn't seem broken to me. How warm does it run just idling (versus what ambient temperature where you are)? > I looked at acpi_thermal, have to digest it. > > Found the source online for freebsd acpi. It'll be on your disk if you installed sources. > So I guess that I could adjust the throttling, through the process that > the machine uses to save power?? I wouldn't worry about that. Are you not running powerd(8)? As Kevin Oberman often points out, p4tcc is for thermal control - as we've just exercised - but cpufreq(4), controlled by powerd, is the way to save power when you don't need the CPU running at maximum frequency, which is likely most times. Running it slower when idle _greatly_ reduces heat. cheers, Ian From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 23 11:06:43 2013 Return-Path: Delivered-To: freebsd-acpi@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 ESMTPS id 58E5A4CF for ; Mon, 23 Dec 2013 11:06:43 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2A4DC11AC for ; Mon, 23 Dec 2013 11:06:43 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rBNB6hw0029910 for ; Mon, 23 Dec 2013 11:06:43 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rBNB6gPG029908 for freebsd-acpi@FreeBSD.org; Mon, 23 Dec 2013 11:06:42 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Dec 2013 11:06:42 GMT Message-Id: <201312231106.rBNB6gPG029908@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Dec 2013 11:06:43 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/181665 acpi [acpi] System will not go into S3 state. o kern/180897 acpi [acpi] ACPI error with MB p8h67 v.1405 o kern/174766 acpi [acpi] Random acpi panic o kern/174504 acpi [ACPI] Suspend/resume broken on Lenovo x220 o kern/173408 acpi [acpi] [regression] ACPI Regression: battery does not o kern/171305 acpi [acpi] acpi_tz0: _CRT value is absurd, ignored (256.0C o kern/165381 acpi [cpufreq] powerd(8) eats CPUs for breakfast o kern/164329 acpi [acpi] hw.acpi.thermal.tz0.temperature shows strange v o kern/162859 acpi [acpi] ACPI battery/acline monitoring partialy working o kern/161715 acpi [acpi] Dell E6520 doesn't resume after ACPI suspend o kern/161713 acpi [acpi] Suspend on Dell E6520 o kern/160838 acpi [acpi] ACPI Battery Monitor Non-Functional o kern/160419 acpi [acpi_thermal] acpi_thermal kernel thread high CPU usa o kern/158689 acpi [acpi] value of sysctl hw.acpi.thermal.polling_rate ne o kern/154955 acpi [acpi] Keyboard or ACPI doesn't work on Lenovo S10-3 o kern/152098 acpi [acpi] Lenovo T61p does not resume o i386/146715 acpi [acpi] Suspend works, resume not on a HP Probook 4510s o kern/145306 acpi [acpi]: Can't change brightness on HP ProBook 4510s o i386/143798 acpi [acpi] shutdown problem with SiS K7S5A o kern/143420 acpi [acpi] ACPI issues with Toshiba o kern/142009 acpi [acpi] [panic] Panic in AcpiNsGetAttachedObject o kern/139088 acpi [acpi] ACPI Exception: AE_AML_INFINITE_LOOP error o amd64/138210 acpi [acpi] acer aspire 5536 ACPI problems (S3, brightness, o i386/136008 acpi [acpi] Dell Vostro 1310 will not shutdown (Requires us o kern/132602 acpi [acpi] ACPI Problem with Intel SS4200: System does not a i386/122887 acpi [panic] [atkbdc] 7.0-RELEASE on IBM HS20 panics immed s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/73823 acpi [request] acpi / power-on by timer support 28 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 23 20:30:32 2013 Return-Path: Delivered-To: freebsd-acpi@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 ESMTPS id C630A19E for ; Mon, 23 Dec 2013 20:30:32 +0000 (UTC) Received: from frontend2.warwick.net (mx1.warwick.net [204.255.24.103]) by mx1.freebsd.org (Postfix) with SMTP id 5C9281DF1 for ; Mon, 23 Dec 2013 20:30:31 +0000 (UTC) Received: (qmail 13517 invoked from network); 23 Dec 2013 20:23:50 -0000 Received: from 70.44.113.171.res-cmts.sefg.ptd.net (HELO [70.44.113.171]) (egunther@warwick.net@70.44.113.171) by frontend2.warwick.net with SMTP (2231693c-6c10-11e3-acec-001f2909bf3e); Mon, 23 Dec 2013 15:23:50 -0500 Message-ID: <1387830229.6690.33.camel@res-cmts> Subject: Re: loud fan pavilion ze2000 From: ito To: Sulev-Madis Silber Date: Mon, 23 Dec 2013 15:23:49 -0500 In-Reply-To: <52B653AD.7090705@hot.ee> References: <1387551635.2533.21.camel@res-cmts> <20131221152703.E25305@sola.nimnet.asn.au> <1387666895.5356.22.camel@res-cmts> <52B653AD.7090705@hot.ee> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.4 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-MagicMail-UUID: 2231693c-6c10-11e3-acec-001f2909bf3e X-MagicMail-Authenticated: egunther@warwick.net Cc: freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Dec 2013 20:30:32 -0000 On Sun, 2013-12-22 at 04:51 +0200, Sulev-Madis Silber wrote: > No, that's a disk filler :) Also useful sometimes... > Thanks > For CPU load test one needs "dd if=/dev/urandom of=/dev/null" (might > want to run it hw.ncpu times to cover all). Just watch out, dd is one of > those tools which can easily bring disaster into house. > That's my opinion, though without first hand knowledge. > On 2013-12-22 01:01, ito wrote: > > PS, is this the exact command? > > " dd if=/dev/random > of=/dev/null " thanks, eg From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 23 20:31:24 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5EE5D1EC for ; Mon, 23 Dec 2013 20:31:24 +0000 (UTC) Received: from frontend2.warwick.net (mx1.warwick.net [204.255.24.103]) by mx1.freebsd.org (Postfix) with SMTP id 1F8C71DFC for ; Mon, 23 Dec 2013 20:31:24 +0000 (UTC) Received: (qmail 20985 invoked from network); 23 Dec 2013 20:31:23 -0000 Received: from 70.44.113.171.res-cmts.sefg.ptd.net (HELO [70.44.113.171]) (egunther@warwick.net@70.44.113.171) by frontend2.warwick.net with SMTP (3018f136-6c11-11e3-9e88-001f2909bf3e); Mon, 23 Dec 2013 15:31:23 -0500 Message-ID: <1387830682.6690.38.camel@res-cmts> Subject: Re: loud fan pavilion ze2000 From: ito To: Ian Smith Date: Mon, 23 Dec 2013 15:31:22 -0500 In-Reply-To: <20131222153537.T25305@sola.nimnet.asn.au> References: <1387551635.2533.21.camel@res-cmts> <20131221152703.E25305@sola.nimnet.asn.au> <1387666895.5356.22.camel@res-cmts> <20131222153537.T25305@sola.nimnet.asn.au> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.4 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-MagicMail-UUID: 3018f136-6c11-11e3-9e88-001f2909bf3e X-MagicMail-Authenticated: egunther@warwick.net Cc: freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Dec 2013 20:31:24 -0000 On Sun, 2013-12-22 at 16:51 +1100, Ian Smith wrote: > On Sat, 21 Dec 2013 18:01:35 -0500, ito wrote: > > Hello Ian, > > > > At 50 through 62C the dev.cpu.0.freq: 1298 > > > > at 70C , 1135 > > > > back up to 1298 > > Right, 1135 / 1298 ~= .875 = 7/8, so yes that's your 1.3GHz CPU dropping > down one step for thermal control. OK > > dev.cpu.0.freq_levels: 1298/-1 1298/-1 973/-1 811/-1 > > 649/-1 486/-1 324/-1 162/-1 > > > > Also directly below that: > > > > dev.p4tcc.0.freq_settings: 10000/-1 8750/-1 7500/-1 6250/-1 5000/-1 > > 3750/-1 2500/-1 1250/-1 > > > > I suppose that is the 8 (freq_levels) you where referring to. Further I > > infer that this -1 means that the BIOS has set them or does set them. > Yes, but here the -1 indicates for freq_levels that power consumption in milliwatts at that freq is unknown, likely the same for p4tcc settings. Ok. > > I set hw.acpi.thermal.tz0._PSV: 70C > > > > Trying "find / acpi" to see it work. > > > > While doing the above (find) the fan is on but not full out. > > find(1) works disk harder than CPU as a rule, though here that command > gets xorg about 70% busy, and keeps going for ages after hitting ^C, as > it lists each file on the disk :) Maybe useful: find / -name "*acpi*" OK, I will keep that in mind find / -name "*acpi*" > From below: > > PS, is this the exact command? > > " dd if=/dev/random > of=/dev/null " > > No, no. I was careful to be precise, and yes a mistyped dd can be > dangerous, and redirected to a file could indeed fill your disk. > Fortunately that one doesn't work, invalid filename. see dd(1). > OK so "dd if=/dev/urandom of=/dev/null" I see: if=FILE read from file instead of stdin /dev/urandom, kernels random number generator of=FILE write to FILE instead of stdout /dev/null, data sink : > > I am reluctant to type anything like dd: anything: I'm not really that > > confident with the command line. > > Without your redirection it just reads from /dev/random, burning CPU, > discarding the output, until you hit ^C .. perfectly safe. > :> > > After setting the PSV value it does not go above 71 when rendering > > animation with blender. > > Yeah rendering will busy the CPU (and GPU too) pretty well. Good, so > we know passive cooling works (in case your fan ever really packs up). > The passive cooling seems to work pretty well. :0 > > I will try cleaning it again, but I think I remember that I thought > > cleaning would fix it before. > > Unless you live in an extraordinarily dust-free environment, this needs > doing with some regularity anyway. I did mine the other day, as summer > ambient temperatures over 30C are becoming normal here (happy solstice!) > I did a quick cleaning but did not want to take it apart at the moment. However, I noticed in the past that a thorough cleaning only helped but did not solve noise. > At the temperatures you've quoted, apart from annoying fan noise, it > doesn't seem broken to me. How warm does it run just idling (versus > what ambient temperature where you are)? > Yeah, thats the thing this is an old computer and all but it still works +stock+ more or less. That is one of the few things that is actually bothersome, the fan that is. I do not have AC but the window is often open, it is winter here. I would guess between 60-70 degrees Fahrenheit (15-21C). > > I looked at acpi_thermal, have to digest it. > > > > Found the source online for freebsd acpi. > > It'll be on your disk if you installed sources. > I did not install the sources, although I did find acpiio.h in /usr/include/dev/acpica/ so I may try the find command you mentioned (find -name "*acpi*") and see what else I can find. And as I mentioned I can find it online. > > So I guess that I could adjust the throttling, through the process that > > the machine uses to save power?? > > I wouldn't worry about that. Are you not running powerd(8)? As Kevin > Oberman often points out, p4tcc is for thermal control - as we've just > exercised - but cpufreq(4), controlled by powerd, is the way to save > power when you don't need the CPU running at maximum frequency, which is > likely most times. Running it slower when idle _greatly_ reduces heat. Powerd is the first thing that was mentioned on the FreeBSD forums. I tried it but possibly did not configure it properly. It did not seem to fix the fan issue and as I said above the computer works fine otherwise; no emergency shut down's or slow downs really to speak of. I don't really work this computer that hard so I am not demanding too much out of it. Which is why I thought maybe the 'normal' operation of the CPU could be curtailed. ----- -----------/etc/rc.conf---------- ----snip----- powerd_enable="YES" powerd_flags="-a adp -b min -i 30" ------snip------ ----------------------- ------ --I am trying powerd -i 30 to see where it gets me. > cheers, Ian Thanks a bunch, eg