Resume failed after Suspend on Thinkpad x201i

[乔楚]

2012/8/5 matt <sendtomatt at gmail.com>:
> On 08/03/12 23:39, 乔楚 wrote:
>>
>> 2012/8/3 Zack Breckenridge <zbrdge at gmail.com>:
>>>
>>> First of all, let me note that the Kernel config file I posted was for
>>> 10.0-CURRENT (a few weeks back now though).
>>>
>>> I've been looking into it, but still haven't developed a patch yet. I
>>> have verified that the screen blanking issue, on my hardware, occurs
>>> somewhere in the vm86 mode emulation code (which is how VESA is
>>> implemented on amd64), ultimately called by vesa_bios_post(), which is
>>> called in turn by vesa_load_state() on resume [see:
>>> http://fxr.watson.org/fxr/source/dev/fb/vesa.c?im=3#L1497].
>>> vesa_bios_post() ultimately calls x86bios_call() [see:
>>> http://fxr.watson.org/fxr/source/compat/x86bios/x86bios.c?im=10#L584]
>>> and emulates the real mode VESA "initialization" code with a call to
>>> x86emu_exec_call().
>>>
>>> I think in order to figure out whats going on from here I will have to
>>> do some DDB scripting and capture the output. I don't believe remote
>>> debugging will be possible with my hardware (no serial, no
>>> firewire)... Anyway, I'm working on it.
>>>
>>> So to verify that we are having the same issue, you can take the
>>> following steps:
>>>
>>> 1) build a kernel with debugging and VESA enabled:
>>>      options VESA
>>>      options KDB
>>>      options DDB
>>> 2) disable X, boot into the console and issue the following commands:
>>>      # sysctl debug.acpi.suspend_bounce=1
>>>      # sysctl debug.kdb.enter=1
>>>      db> break x86emu_exec_call
>>>      db> c
>>>      # zzz
>>>      [you should hit the breakpoint]
>>>      db> bt
>>>      x86emu_exec_call() ...
>>>      vesa_bios_post() ...
>>>      ... rest of backtrace ...
>>>      db> c
>>> 3) after hitting that last c, your screen should go black. Then you
>>> should be able to type "reboot" and reboot cleanly
>>
>> My screen go black, but type "reboot" no effect. I can be sure to type
>> "reboot" and return.
>> LED status:
>> 1. Disk LED is light, and off at a moment.
>> 2. "Z" LED is light, Battary and power LED is light.
>> 3. Wifi LED is light.
>>
>>> I'm pretty sure that if you get the same results, we are having the
>>> same issue, though I can make no guarantees.
>>>
>>>
>> When I shutdown from KDE, or type shutdown -p now from console, my
>> laptor can't shutdown complete.
>> The battary LED is light alawys, others LED is off, and vents of the
>> laptor has been blowing hot air.
>> _______________________________________________
>> freebsd-acpi at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
>> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe at freebsd.org"
>>
> Honest Qiao: Regarding hot air, are you running powerd? Try "powerd -a
> adaptive -b adaptive" as root and wait 5 minutes to see if the hot air
> stops. If it works, try "man powerd" for installation instructions. Lenovo
> laptops are thermally designed for low CPU utilization. I can almost boil
> water on mine during buildworld. Without powerd, they run at full thermal
> profile and act as excellent hand warmers.
>
> Zack: Regarding remote debugging, do you have an expresscard/cardbus/etc
> slot? Although hard to find you may be able to find a firewire card for
> that. Not sure if that would work or not...same goes for a USB->Serial
> console, my guess is that it wouldn't work?
>
> Matt

Regarding powerd:
I know powerd.
I also set it autostart in rc.conf:
powerd_enable="YES"
powerd_flags="-a adaptive -b adaptive"
And I know that sysctl named dev.cpu.0.freq will change between 333 to
2333 with system load.

But, When I shutdown the system, the battery indicator finally closed,
the fan also continue to operate;
Because the fan is in operation, and blow hot air, indicating that the
CPU does not really stop working.

So my system did not really close.If I do not press the power button
to force shut down the power supply, the battery LED is always on,
whether connected to AC power.
If I accidentally put it in a laptor bag, he will become hot.


Regarding extend slot:
Lenovo thinkpad x201 only has USB slot. It hasn't Serial slot.
I also think that a USB => serial can not be with the remote debugging.