From owner-freebsd-acpi@FreeBSD.ORG Thu Apr 7 17:15:21 2005 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 51D3D16A4CE for ; Thu, 7 Apr 2005 17:15:21 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id F05C243D46 for ; Thu, 7 Apr 2005 17:15:20 +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 j37HFHLS008092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 7 Apr 2005 10:15:17 -0700 Message-ID: <42556AA3.5040403@root.org> Date: Thu, 07 Apr 2005 10:15:15 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <42552573.6040902@centtech.com> In-Reply-To: <42552573.6040902@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: Suspend powers off machine 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: Thu, 07 Apr 2005 17:15:21 -0000 Eric Anderson wrote: > I'm going to have some time on my hands next week, and I'd like to hunt > down an issue with my laptop. When attempting to go into S3, instead of > going into S3, it powers off (uncleanly). Can anyone tell me where this > might be happening in the code, so I can start the printf debugging > process? It's nearly 100% certain it happens in AcpiEnterSleepState at the write to PM1A. This is in sys/contrib/dev/acpica/hwsleep.c In thinking about it, my best theory is that the southbridge interprets this write as an S4/S5 transition. Perhaps the ASL gives the wrong value to write? Perhaps the chipset is not being prepared for S3 correctly. In any case, better chipset specs would probably help diagnose this. Other possibilities are that the setting of SLP_EN should be done at the same time as the write with the SLP_TYP value (i.e. write SLP_TYPE_S3|SLP_EN instead of splitting the write into two phases). It also may be that the previous steps like disabling BM ctrl are not appropriate for some chipsets. If you can get more info, I can refine this theory. -- Nate