From owner-freebsd-acpi@FreeBSD.ORG Wed May 3 14:04:42 2006 Return-Path: X-Original-To: freebsd-acpi@FreeBSD.org Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9498716A421; Wed, 3 May 2006 14:04:42 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 816F143D45; Wed, 3 May 2006 14:04:41 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.138] (helo=anti-virus01-09) by smtp-out3.blueyonder.co.uk with smtp (Exim 4.52) id 1FbHy4-0002HO-7l; Wed, 03 May 2006 15:04:40 +0100 Received: from [80.192.58.117] (helo=[192.168.0.2]) by asmtp-out2.blueyonder.co.uk with esmtp (Exim 4.52) id 1FbHy0-0003JX-GI; Wed, 03 May 2006 15:04:36 +0100 Message-ID: <4458B873.2020608@dial.pipex.com> Date: Wed, 03 May 2006 15:04:35 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: Pav Lucistnik References: <1146231595.94164.25.camel@pav.hide.vol.cz> <20060502154819.GA16135@poupinou.org> <1146585606.31507.38.camel@pav.hide.vol.cz> <20060503134248.GB31815@poupinou.org> In-Reply-To: <20060503134248.GB31815@poupinou.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: acpi_thermal on nforce 4 board X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 14:04:42 -0000 Bruno Ducrot wrote: >then we should be able to get correct values, but the >chip could hang in the long run. > > Running mbmon throughout the day I see approximately one such hang a day, and it seems to cause temps to spike as well. I now do this to limit the damage: (ulimit -t 1; /usr/local/bin/mbmon -p winbond -c 1) > >BTW I don't see why mbmon failed. Maybe you should >try something like that: > >mbmon -P winbond > > Also for some winbond chips healthd can work where mbmon doesn't. --Alex