From owner-freebsd-acpi@FreeBSD.ORG Wed Oct 22 21:27:52 2008 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 B554710656A1; Wed, 22 Oct 2008 21:27:52 +0000 (UTC) (envelope-from nate@root.org) Received: from fulgencio.claresco.com (209-128-117-004.BAYAREA.NET [209.128.117.4]) by mx1.freebsd.org (Postfix) with ESMTP id 9516C8FC0C; Wed, 22 Oct 2008 21:27:52 +0000 (UTC) (envelope-from nate@root.org) Received: from [10.0.8.5] (fw.claresco.com [209.128.117.3]) by fulgencio.claresco.com (Postfix) with ESMTP id 1730E1339C4; Wed, 22 Oct 2008 14:27:52 -0700 (PDT) Message-ID: <48FF9AFA.3030201@root.org> Date: Wed, 22 Oct 2008 14:28:26 -0700 From: Nate Lawson User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Alexander Motin References: <1224616985.00027652.1224606603@10.7.7.3> <48FF78F0.2090801@FreeBSD.org> <200810221623.09613.jkim@FreeBSD.org> <48FF9925.4090007@FreeBSD.org> In-Reply-To: <48FF9925.4090007@FreeBSD.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: Semi-working patch for amd64 suspend/resume 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: Wed, 22 Oct 2008 21:27:52 -0000 Alexander Motin wrote: > Jung-uk Kim wrote: >> When you do 'sysctl debug.acpi.suspend_bounce=1' and 'acpiconf -s 3', >> does it bounce back? If it does not, there are other problems, e.g., >> device drivers. On my desktop, for example, vga(4) tries to restore >> previous state while resuming but it hangs system. In fact, I believe >> ISA-era EGA/VGA save/restore routines do not work for modern graphics >> cards at all. :-( > > Test passed from both console and XOrg. I have integrated i965GM video. > > Here is verbose messages from that trip "there and back again": > > Oct 23 00:11:55 mavbook acpi: suspend at 20081023 00:11:55 > Oct 23 00:12:00 mavbook kernel: vga0: saving 68 bytes of video state > Oct 23 00:12:00 mavbook kernel: pci0:0:2:0: Transition from D0 to D3 > Oct 23 00:12:00 mavbook kernel: pci0:0:2:1: Transition from D0 to D3 > Oct 23 00:12:00 mavbook kernel: pci0:0:26:7: Transition from D0 to D3 > Oct 23 00:12:00 mavbook kernel: acpi: bad write to port 0x080 (32), val > 0xbb > Oct 23 00:12:06 mavbook kernel: pci0:0:27:0: Transition from D0 to D3 > Oct 23 00:12:06 mavbook kernel: pci0:0:31:2: Transition from D0 to D3 > Oct 23 00:12:06 mavbook kernel: pci0:0:2:0: Transition from D3 to D0 > Oct 23 00:12:06 mavbook kernel: pci0:0:2:1: Transition from D3 to D0 > Oct 23 00:12:06 mavbook kernel: acpi: bad write to port 0x080 (32), val > 0xaa > Oct 23 00:12:06 mavbook kernel: pci0:0:26:7: Transition from D3 to D0 > Oct 23 00:12:06 mavbook kernel: pci0:0:27:0: Transition from D3 to D0 > Oct 23 00:12:06 mavbook kernel: pci0:0:31:2: Transition from D3 to D0 That's kind of weird. The above devices were turned off (D3) then back on again (D0). I'm wondering about that blocked write also. -- Nate