Date: Fri, 10 Dec 2004 10:43:26 -0800 From: Nate Lawson <nate@root.org> To: Ulrich Spoerlein <q@uni.de> Cc: acpi@FreeBSD.org Subject: Re: suspend/resume improved? Message-ID: <41B9EE4E.8030703@root.org> In-Reply-To: <20041210180446.GA768@galgenberg.net> References: <41B4E577.9060502@root.org> <41B50754.10604@centtech.com> <41B50C12.6070103@root.org> <20041208095845.GA896@galgenberg.net> <41B76AF2.3040204@root.org> <20041210180446.GA768@galgenberg.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Ulrich Spoerlein wrote:
> On Wed, 08.12.2004 at 12:58:26 -0800, Nate Lawson wrote:
>
>>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
>
>
> Line 444 is the culprit:
> ACPI_FLUSH_CPU_CACHE ();
>
> Status = AcpiHwRegisterWrite (ACPI_MTX_DO_NOT_LOCK, ACPI_REGISTER_PM1A_CONTROL, PM1AControl);
> if (ACPI_FAILURE (Status))
> {
> return_ACPI_STATUS (Status);
> }
>
> Putting the loop before AcpiHwRegisterWrite will enter infinite loop,
> putting it after it -> Reset
Interesting. If you add a "DELAY(10000);" before the register write,
does this help? A more likely issue is that we need to write pm1a/b at
the same time. Let me think about this and get you more info later.
--
Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41B9EE4E.8030703>