public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Jeff Trull <linmodemstudent@gmail.com>
Cc: linux-acpi@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Pavel Machek <pavel@suse.cz>
Subject: Re: no self-refresh during S3 - any debug hints?
Date: Thu, 19 Jun 2008 15:02:12 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0806191437580.3040@localhost.localdomain> (raw)
In-Reply-To: <685450530805311215lf463875g8eed40da630b4f96@mail.gmail.com>



On Sat, 31 May 2008, Jeff Trull wrote:

> I made a breakthrough in my s2r debugging last night when I realized
> that the sooner I pressed the power button after suspend, the more
> life the system exhibited post-resume.  In fact when I attempted to
> resume immediately after entering suspend, my system had a successful
> resume from memory for the first time ever.  Therefore, I have a new
> hypothesis: DRAM self-refresh mode is not being properly entered.
> 
> I'm running kernel 2.6.20 on a laptop with an ATI IGP 320M Northbridge
> and an Athlon XP.  DSDT has a _PTS but no _GTS.  I'm comfortable
> recompiling the kernel.  Any suggestions as to how to proceed,
> experiments to run, etc.?

Start by running the upstrteam kernel -- now 2.6.26, just out of 
principle.

Then, see Documentation/power/basic-pm-debugging.txt

and try the options in /sys/power/pm_test

If the cause is as you suspect, they should all work.
If any of them fail, then there is a problem elsewhere.

eg. the deepest test is core:

# echo core > /sys/power/pm_test
# echo mem > /sys/power/state

should work, because it does everything except actually leap into
the BIOS to enter self-refresh.

# echo none > /sys/power/pm_test

then disalbes this test mode.

-Len




  parent reply	other threads:[~2008-06-19 19:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-31 19:15 no self-refresh during S3 - any debug hints? Jeff Trull
2008-05-31 20:25 ` Matthew Garrett
2008-06-19 15:09 ` Matthew Garrett
2008-06-19 16:40   ` Jeff Trull
2008-07-27 20:22     ` Jeff Trull
2008-06-19 19:02 ` Len Brown [this message]
2008-06-19 19:26   ` Jeff Trull
2008-06-19 20:10   ` Pavel Machek
2008-06-21  6:13     ` Jeff Trull
2008-06-23 10:15       ` Pavel Machek

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=alpine.LFD.1.10.0806191437580.3040@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=linmodemstudent@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=rjw@sisk.pl \
    /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