Date: Wed, 03 May 2006 15:04:35 +0100 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: Pav Lucistnik <pav@FreeBSD.org> Cc: freebsd-acpi@FreeBSD.org Subject: Re: acpi_thermal on nforce 4 board Message-ID: <4458B873.2020608@dial.pipex.com> In-Reply-To: <20060503134248.GB31815@poupinou.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4458B873.2020608>