From owner-freebsd-acpi@FreeBSD.ORG Sun Aug 5 07:14:52 2012 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D2F8106566C for ; Sun, 5 Aug 2012 07:14:52 +0000 (UTC) (envelope-from honestqiao@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id A7D048FC0C for ; Sun, 5 Aug 2012 07:14:51 +0000 (UTC) Received: by vbmv11 with SMTP id v11so575831vbm.13 for ; Sun, 05 Aug 2012 00:14:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=uJnj0p1VTlnGyzhd5Z9zDjMwr4VWWs9p0jURl13t8vQ=; b=QgrXhGxX9P0YsDxDdersnjuyIU3Lgo0phm5oo8Byh0rrqeIcw/QF5p34IjvH/xUkwD kiqs+CX6R47cQOD2sGysQfaVidyNF5+1D/Kh0JxG0rGjBYsne68MNQn2XI6ZYdRJe7Q5 YWnmvQJxDZvJ++To3ST6uWI7bdbXheLn95r5sKA2TZ0DXFzUKG0yaBxnnpmVx8jPqmZI lT1v+Gf7BY+xICdiPJBRPOzEpXO7SNBB7gDn/7J5CNnpDAyoV9DRNqDiliuBjT+tBDNb 6Pr/8geC5EQ4WVxBk3wuU5En27J9AbqUpvI/MXR8ZhhC7DmA683HEKZDeyqzkxXO9aRl gJbg== Received: by 10.59.8.37 with SMTP id dh5mr6115685ved.2.1344150883880; Sun, 05 Aug 2012 00:14:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.231.199 with HTTP; Sun, 5 Aug 2012 00:14:03 -0700 (PDT) In-Reply-To: <501DA226.8000707@gmail.com> References: <201207021729413382845@gmail.com> <4FF2599B.6050409@gmail.com> <201207031411248300207@gmail.com> <1341437029.4017.5.camel@localhost> <2012072016090861869410@gmail.com> <2012080201072126960020@gmail.com> <501DA226.8000707@gmail.com> From: =?UTF-8?B?5LmU5qWa?= Date: Sun, 5 Aug 2012 15:14:03 +0800 Message-ID: To: matt Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-acpi Subject: Re: Resume failed after Suspend on Thinkpad x201i 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: Sun, 05 Aug 2012 07:14:52 -0000 2012/8/5 matt : > On 08/03/12 23:39, =E4=B9=94=E6=A5=9A wrote: >> >> 2012/8/3 Zack Breckenridge : >>> >>> 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=3D3#L1497]. >>> vesa_bios_post() ultimately calls x86bios_call() [see: >>> http://fxr.watson.org/fxr/source/compat/x86bios/x86bios.c?im=3D10#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=3D1 >>> # sysctl debug.kdb.enter=3D1 >>> 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@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi >> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@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. Lenov= o > 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=3D"YES" powerd_flags=3D"-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 =3D> serial can not be with the remote debugging.