public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: [Fwd: Suspend powers off machine]
Date: Tue, 12 Apr 2005 12:06:48 -0700	[thread overview]
Message-ID: <425C1C48.60600@root.org> (raw)

It seems on Eric's Dell D600, entering S3 powers off the system (similar 
to S5).  It also apparently works on Linux.  Anyone have an idea what 
we're doing wrong?

Thanks,
Nate

-------- Original Message --------
Subject: Re: Suspend powers off machine
Date: Mon, 11 Apr 2005 22:06:52 -0500
From: Eric Anderson <anderson-EcDrcr+ShHtWk0Htik3J/w@public.gmane.org>
References: <42552573.6040902-EcDrcr+ShHtWk0Htik3J/w@public.gmane.org> <42556AA3.5040403-Y6VGUYTwhu0@public.gmane.org>

Nate Lawson wrote:
> 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

You're right - it happens here:
Status = AcpiHwRegisterWrite (ACPI_MTX_DO_NOT_LOCK, 
ACPI_REGISTER_PM1A_CONTROL, PM1AControl);
In that subroutine..

> 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


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

                 reply	other threads:[~2005-04-12 19:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=425C1C48.60600@root.org \
    --to=nate-y6vguytwhu0@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox