From owner-freebsd-current@FreeBSD.ORG Fri Dec 12 13:57:35 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3332416A4CE for ; Fri, 12 Dec 2003 13:57:35 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 38BC443D35 for ; Fri, 12 Dec 2003 13:57:34 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 53997 invoked by uid 1000); 12 Dec 2003 21:57:35 -0000 Date: Fri, 12 Dec 2003 13:57:35 -0800 (PST) From: Nate Lawson To: Guido van Rooij In-Reply-To: <20031212185907.GA61783@gvr.gvr.org> Message-ID: <20031212135444.B53967@root.org> References: <20031209114400.G43006@root.org> <20031212185907.GA61783@gvr.gvr.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "Sergey A. Osokin" cc: current@freebsd.org Subject: Re: ACPI problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 21:57:35 -0000 On Fri, 12 Dec 2003, Guido van Rooij wrote: > On Tue, Dec 09, 2003 at 11:58:30AM -0800, Nate Lawson wrote: > > Suspend/resume will continue to be a problem area for some time. Perhaps > > I should put up a FAQ about this. > > > > 1. Try different states (S1-S4) and see if one of them works. > > I have a system where S3 leads to an immediate reboot. S4 leads to > a hang. S2 is not available. > S1 leads to a nice suspend, except that the LCD is not powered off. > Resume works okay. > When I push the lid button when in the boot loader, the LCD is powered > off. In Windows everything works like expected. In the loader, the BIOS is still controlling the display. Since you mention that S1 works on recent Linux kernels for your D600, I'll look into what we do differently. It appears only S1 and S5 are working for Linux. > This is a Dell D600. S4 is handled by Windows itsself. Does this mean > the BIOS doesn't support doing it itself? Yes, we haven't implemented S4-OS yet. To do this, we need to modify the dump routine to do a kernel dump and then modify loader to recognize the dump and load it and resume rather than booting the OS. This is non-trivial work and I'm not likely to get to it any time soon. > > 2. Try tunable/sysctl hw.acpi.reset_video=0 > > > > 3. Try tunable/sysctl hw.syscons.sc_no_suspend_vtswitch=1 > > > > 4. Try sysctl hw.acpi.sleep_delay=0 > > (I take it these are all for systems where resume doesnt work properly?) Yes. -Nate