From: Pavel Machek <pavel@suse.cz>
To: Jeff Trull <linmodemstudent@gmail.com>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: no self-refresh during S3 - any debug hints?
Date: Mon, 23 Jun 2008 12:15:08 +0200 [thread overview]
Message-ID: <20080623101508.GA3003@elf.ucw.cz> (raw)
In-Reply-To: <685450530806202313v4ec63bc8n5213330d77e1b6d@mail.gmail.com>
On Fri 2008-06-20 23:13:06, Jeff Trull wrote:
> On Thu, Jun 19, 2008 at 1:10 PM, Pavel Machek <pavel@suse.cz> wrote:
>
> >
> > 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.
>
> I don't have ready access to 2.6.26, but with 2.6.24 s3_beep produces
> a (endless, loud) tone if I resume immediately after suspend, and
> nothing at all if I wait 10 seconds first.
Hmm, okay, that confirms your theory :-(. Contacting BIOS vendor and
looking in DSDT for something strange turning off autorefresh is
something you could try...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2008-06-23 10:14 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
2008-06-21 6:13 ` Jeff Trull
2008-06-23 10:15 ` Pavel Machek [this message]
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=20080623101508.GA3003@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