Troubles with ACPI on HP nx5000 laptop
null at bikeman.ru
Thu Nov 11 01:33:04 PST 2004
Nate Lawson wrote:
>> > ps
>> 45 c15b8c5c d4de5000 0 0 0 0000204 [RUNQ]
>> > trace 45
>> sched_switch(c155f640,0,1,5e21f7f1,5e141b1) at sched_switch+0x160
>> mi_switch(1,0,d3becca8,10) at mi_switch+0x1d9
>> sleepq_switch(c07a4694,c155f640,d3becce0,c04e1dcc,c07a4694) at
>> sleepq_timedwait(c07a4694,54,c07a46a0,c07a0150,0) at
>> msleep(c07a4694,c07a46a0,254,c07a0150,3e8) at msleep+0x3bc
>> acpi_tz_thread(0,d3becd48,68bf09fc,85e800c6, 2c483cd) at
>> fork_exit(c07902f0,0,d3becd48) at fork_exit+0x80
>> fork_trampoline() at fork_trampoline+0x8
>> --- trap 0x1, eip = 0, esp = 0xd3becd7c, ebp = 0 ---
> This looks normal. It just means there's no work for the thermal thread
> to do so it sleeps. I wonder why it's on the RUNQ though?
> Please recompile your acpi module with options ACPI_DEBUG. Then set
> this at the loader prompt or in loader.conf:
> debug.acpi.level="ACPI_LV_OBJECTS ACPI_LV_ALL_EXCEPTIONS"
> Send me the output after a hang.
THERMAL-0507  acpi_tz_switch_cooler_: called to turn \_TZ_.C205 off
THERMAL-0535  acpi_tz_switch_cooler_: called to turn \_TZ_.C204 on
After output everything worked for 2-3 seconds and then hung.
>> Furthermore, after "cont" in ddb, everything worked for a few
>> seconds. And it always works for a while till hangs again if after
>> hanging I call ddb and type "cont". Maybe it will "unhang" if I
>> wait till CPU gets cold.
> If you have a serial console, a ps on all threads once it hangs would be
I don't. But if it's very important, i can make a photo. :-)
More information about the freebsd-acpi