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

On Thu 2008-06-19 15:02:12, Len Brown wrote:
> 
> 
> 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.

Hmm, or some other hardware... I ve seen machines where video ram was
not refreshed. If that piece of hw is critical enough, it will break
resume.

You could try with minimal system, with as little drivers as
possible... use acpi_sleep=s3_beep to determine where it fails.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2008-06-19 20:52 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
2008-06-19 19:26   ` Jeff Trull
2008-06-19 20:10   ` Pavel Machek [this message]
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=20080619201052.GA15587@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=lenb@kernel.org \
    --cc=linmodemstudent@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --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