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: Re: Dell Inspiron 510m sleep states S3/S4 not working]
Date: Sat, 05 Mar 2005 23:31:51 -0800	[thread overview]
Message-ID: <422AB1E7.4050304@root.org> (raw)

I have reports that Linux works for S3 on these machines but FreeBSD 
does not.  The Dell Inspiron 510M at least has a problem where the write 
to PM1A in hwsleep.c resets the system instead of entering S3.  I heard 
that Linux had similar problems in the past but now works.  Can someone 
let me know what was going on?

Thanks much,
Nate

-------- Original Message --------
Subject: Re: Dell Inspiron 510m sleep states S3/S4 not working
Date: Sat, 05 Mar 2005 20:02:44 -0500
From: Igor Partola <ipartola-27MbaEWyEdNeoWH0uzbU5w@public.gmane.org>
To: freebsd-acpi-h+KGxgPPiopAfugRpC6u6w@public.gmane.org

Ulrich Spörlein wrote:

>On Thu, 03.03.2005 at 17:10:25 -0800, Nate Lawson wrote:
>  
>
>>Easiest way to test for resets is to stick this loop in the C code, 
>>pushing it farther down until you identify the line of code that resets 
>>instead of hanging.
>>
>>hang: goto hang;
>>
>>Try this in AcpiEnterSleepState().
>>    
>
>Been there, done that. See
>http://lists.freebsd.org/mailman/htdig/freebsd-acpi/2004-December/000949.html
>
>Ulrich Spoerlein

I just did some testing just to make sure that my system resets on the
same line. Sadly that is the problem, writing PM1A resets the machine.

I also compared the code with hwsleep.c from linux 2.6.10. They almost
exactly the same, except for at one point but that should only affect
S5. Everything else is the same.


-------------------------------------------------------
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_ide95&alloc_id\x14396&op=click

                 reply	other threads:[~2005-03-06  7:31 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=422AB1E7.4050304@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