Date: Thu, 17 Mar 2005 19:21:57 +0200 From: Juho Vuori <juho.vuori@kepa.fi> To: Nate Lawson <nate@root.org> Cc: freebsd-acpi@freebsd.org Subject: Re: hp nx6110 freezes with acpi enabled Message-ID: <4239BCB5.3040102@kepa.fi> In-Reply-To: <42389CD5.7050302@root.org> References: <423889DD.2060504@kepa.fi> <42389CD5.7050302@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Nate Lawson wrote:
> Juho Vuori wrote:
>
>> Hello,
>>
>> I'm experiencing problems with acpi. I'm running RELENG_5 as of
>> 15.3.2005 on hp nx6110 laptop. The system has got intel 910gml
>> chipset, celeron-m processor and other hardware which is probably not
>> that much related to the problem.
>>
>> With acpi enabled, the computer runs fine for about 5 or 10 minutes
>> and then freezes completely. The freeze is fairly predictable, but
>> I'm not sure what causes it (must be acpi related though). If I boot
>> the computer with acpi turned off, everything works fine.
>>
>
> Perhaps it's a thermal problem. Try setting this at the loader prompt
> and see if it helps:
>
> debug.acpi.disabled="thermal"
>
Ok, here are my further discoveries about the situation:
After compiling the kernel with some useless drivers (scsi and network
stuff) removed, the machine won't freeze completely, just for few
seconds. It might have something to do with other things I've done
recently, but the new kernel is the most likely.
The freeze is caused by an interrupt storm, when the temperature
raises/drops above/below _ACx values. I'll get normally around 1
acpi-interrupt every 5 seconds, but around 500 when the temperature
changes like this. I did try disabling apic as was suggested in the
handbook, but it didn't have an effect on this.
I don't know if this is supposed to work, but I tried the following
# sysctl hw.acpi.thermal.tz0.active=1
(or =2 =3, ..) with the intention of changing the speed of the fan. Now,
I couldn't discover any obvious regularity in this, but often lowering
the value causes the fan to stop completely and lowering it still more
causes it to start again (this time faster, which is as it should be). I
have no idea what's going on. It sounds like buggy hardware, no ? Or did
I understand things completely wrong?
Juho Vuori
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4239BCB5.3040102>