From: Maxim Levitsky <maximlevitsky@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: Very rare resume bug
Date: Mon, 02 Mar 2009 02:05:18 +0200 [thread overview]
Message-ID: <1235952318.430.3.camel@maxim-laptop> (raw)
In-Reply-To: <200903012221.12423.rjw@sisk.pl>
On Sun, 2009-03-01 at 22:21 +0100, Rafael J. Wysocki wrote:
> On Sunday 01 March 2009, Maxim Levitsky wrote:
> > I currently am testing suspend/resume on my desktop system.
> > I already kept it in suspend to ram state in 2 weeks, and now
> > I resumed it, and screen didn't came back, I tried switching vts
> > it did seem to help, but then everything hung.
>
> Well, it's difficult to say what problem this is.
I thought that warning that I have seen in the logs is the reason for
this hang as it was vt related.
I have seen patches here that fix very related bug.
I continue this test by only using S2RAM on that system about 4~5 times
a day.
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2009-03-02 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 13:05 Very rare resume bug Maxim Levitsky
2009-03-01 13:17 ` Maxim Levitsky
2009-03-01 21:21 ` Rafael J. Wysocki
2009-03-02 0:05 ` Maxim Levitsky [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=1235952318.430.3.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=linux-pm@lists.linux-foundation.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