From owner-freebsd-current@FreeBSD.ORG Tue Dec 9 11:58:30 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 2862D16A4CF for ; Tue, 9 Dec 2003 11:58:30 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 2987743D09 for ; Tue, 9 Dec 2003 11:58:29 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 43169 invoked by uid 1000); 9 Dec 2003 19:58:30 -0000 Date: Tue, 9 Dec 2003 11:58:30 -0800 (PST) From: Nate Lawson To: "Sergey A. Osokin" Message-ID: <20031209114400.G43006@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: Tue, 09 Dec 2003 19:58:30 -0000 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. 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 5. Try the most recent Linux beta kernel with acpi configured. If it works, then perhaps we can find why. Since we share the ACPI-CA interpreter with Linux, it's likely that they have similar problems. 6. Try disabling drivers that may break resume. In particular, uhci doesn't work right after resume. 7. Try building the acpi kernel module with options ACPI_DEBUG, then setting debug.acpi.layer and debug.acpi.level sysctls to various levels of verbosity right before suspending/resuming. Use a serial console to log the output. Here are some proposed settings: debug.acpi.layer="ACPI_ALL_DRIVERS ACPI_ALL_COMPONENTS" debug.acpi.level="ACPI_LV_IO" -Nate