From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 8 20:58:29 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B56EA16A4CE for ; Wed, 8 Dec 2004 20:58:29 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B7F743D68 for ; Wed, 8 Dec 2004 20:58:29 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iB8KwRC4015541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 8 Dec 2004 12:58:28 -0800 Message-ID: <41B76AF2.3040204@root.org> Date: Wed, 08 Dec 2004 12:58:26 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ulrich Spoerlein References: <41B4E577.9060502@root.org> <41B50754.10604@centtech.com> <41B50C12.6070103@root.org> <20041208095845.GA896@galgenberg.net> In-Reply-To: <20041208095845.GA896@galgenberg.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@FreeBSD.org Subject: Re: suspend/resume improved? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 20:58:29 -0000 Ulrich Spoerlein wrote: > On Mon, 06.12.2004 at 17:49:06 -0800, Nate Lawson wrote: > >>It's pretty straightforward but arduous work. First strip down your >>system, removing all drivers except for the hard drive and keyboard (no >>USB, network, etc.) Don't run X. Try S3. If it works, add back in >>drivers until it fails. >>[Resume not working] > > What can I do, if entering S3 immediately reboots the Laptop (Dell > Inspiron 8600c)? Any output I could capture before it resets itself? > > Ulrich Spoerlein Add an infinite loop at various points in the suspend process until it hangs but doesn't reset. Start with the end of the first function below and work your way backwards. Once you identify the exact place the reset occurs, we can figure out why. Use boot -s to keep from having to fsck on each reset or hang. AcpiEnterSleepState():sys/contrib/dev/acpica/hwsleep.c acpi_sleep_machdep():sys/i386/acpica/acpi_wakeup.c acpi_SetSleepState():sys/dev/acpica/acpi.c. C infinite loop: foo: goto foo; ASM infinite loop: foo: jmp foo -- Nate