From owner-freebsd-current@FreeBSD.ORG Tue Jan 25 02:18:07 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35F6916A4CE; Tue, 25 Jan 2005 02:18:06 +0000 (GMT) Received: from out005.verizon.net (out005pub.verizon.net [206.46.170.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5831343D3F; Tue, 25 Jan 2005 02:18:05 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from RabbitsDen ([70.21.161.195]) by out005.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20050125021804.EEET28362.out005.verizon.net@RabbitsDen>; Mon, 24 Jan 2005 20:18:04 -0600 From: "Alexandre \"Sunny\" Kovalenko" To: Robert Watson In-Reply-To: References: Content-Type: text/plain; charset=iso-8859-5 Date: Mon, 24 Jan 2005 21:16:14 -0500 Message-Id: <1106619375.659.16.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from [70.21.161.195] at Mon, 24 Jan 2005 20:17:59 -0600 cc: current@FreeBSD.org Subject: Re: Notebook fan stuck on? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 02:18:07 -0000 On Mon, 2005-01-24 at 14:49 +0000, Robert Watson wrote: > On Sat, 22 Jan 2005, Alexandre "Sunny" Kovalenko wrote: > > > What does > > > > sysctl hw.acpi.thermal > > > > say? > > > > Starting point would be looking at whether > > > > sysctl hw.acpi.thermal.tzN.temperature > > > > changes with time. (for all N your notebook provided). > > paprika:~> sysctl sysctl hw.acpi.thermal > hw.acpi.thermal.min_runtime: 0 > hw.acpi.thermal.polling_rate: 10 > hw.acpi.thermal.tz0.temperature: 49.5C > hw.acpi.thermal.tz0.active: -1 > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV: -1 > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 98.0C > hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 > > (pause 20 seconds) > > paprika:~> sysctl hw.acpi.thermal.tz0.temperature > hw.acpi.thermal.tz0.temperature: 48.5C > > (pause 10 seconds) > > paprika:~> sysctl hw.acpi.thermal.tz0.temperature > hw.acpi.thermal.tz0.temperature: 53.5C > > (pause 10 seconds) > > paprika:~> sysctl hw.acpi.thermal.tz0.temperature > hw.acpi.thermal.tz0.temperature: 49.5C > > Seems like it's jumping around a bit. A lot, even. However, if I run > sysctl -n hw.acpi.thermal.tz0.temperature in a loop separated by sleep 10, > while running a "du /" the results seem fairly predictable: > > 48.5C > 48.5C > 48.5C > 49.5C > 48.5C > 49.5C > 49.5C > 49.5C > 50.5C > 50.5C > 50.5C > 51.5C > 50.5C > 51.5C > 50.5C > > Other than the critical temperature threshold, is it possible to retrieve > other thresholds from the kernel/ACPI? > > Robert N M Watson > It looks like your ASL does not define ACx thermal objects, which means that your fan control is likely to be hidden inside something which used to be called on the regular basis. In the case of my notebook it was inside the temperature reporting routine. If you would, please, send me output of acpidump -d I might be able to come up with more details. -- Alexandre "Sunny" Kovalenko (Олександр Коваленко)