From owner-freebsd-acpi@FreeBSD.ORG Sat Aug 4 06:39:54 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 C5A1A106566C for ; Sat, 4 Aug 2012 06:39:54 +0000 (UTC) (envelope-from honestqiao@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 76F418FC0A for ; Sat, 4 Aug 2012 06:39:54 +0000 (UTC) Received: by qcsg15 with SMTP id g15so1100564qcs.13 for ; Fri, 03 Aug 2012 23:39:53 -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; bh=mX6108D8mLkvLWiQ7idZTw7FFBrVEh0SJBLNitoaIqA=; b=pekqDDmtaqp0XpQWB837Q8L/5ndHETu3vjhxilvmhvgzlB78bFpMteIKYAU16PzEik w6CyVZt13RmW39mQcEAbMuqx3eigZTlyRDt7bEe5Nr+ZrIl9ca+YSSikjzsz5nAElc4J mGzhSnmWuXZxdOootc1GSNCSOftgPntU3rEatVYhpgTitBwMZyAn3u5fDJos9zFGw+xB N6ZBpvwdiEYJOcdv3HsYvndRDqhYD40+W0nxcfrkSuHf2v0186/YAfOBNRjwTvXgJKzC SrD1wle/v77qnyUW8aNvZsy3qekCTQvZ3MQiWfUWaqK54Jt8gQ7fncP4jbSL8zWTwGqH ybJQ== Received: by 10.224.216.7 with SMTP id hg7mr6939092qab.3.1344062393512; Fri, 03 Aug 2012 23:39:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.68.224 with HTTP; Fri, 3 Aug 2012 23:39:12 -0700 (PDT) In-Reply-To: References: <201207021729413382845@gmail.com> <4FF2599B.6050409@gmail.com> <201207031411248300207@gmail.com> <1341437029.4017.5.camel@localhost> <2012072016090861869410@gmail.com> <2012080201072126960020@gmail.com> From: =?UTF-8?B?5LmU5qWa?= Date: Sat, 4 Aug 2012 14:39:12 +0800 Message-ID: To: Zack Breckenridge Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-acpi Subject: Re: 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: Sat, 04 Aug 2012 06:39:54 -0000 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=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.