From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Ferenc Wagner <wferi@niif.hu>
Cc: linux-pm@lists.linux-foundation.org,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Andrew Morton <akpm@linux-foundation.org>,
yakui.zhao@intel.com, LKML <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [linux-pm] intermittent suspend problem again
Date: Fri, 13 Nov 2009 20:59:46 +0100 [thread overview]
Message-ID: <200911132059.46377.rjw@sisk.pl> (raw)
In-Reply-To: <87my2qwff8.fsf@tac.ki.iif.hu>
On Friday 13 November 2009, Ferenc Wagner wrote:
> "Rafael J. Wysocki" <rjw@sisk.pl> writes:
>
> > Yes, echo "core" to /sys/power/pm_test before executing s2disk.
>
> It snapshots the system and returns, producing the same console output
> as s2ram (is this the expected behaviour?) I ran this several times in
> a loop, and experienced no problems at all. Maybe it depends on the
> amount of memory used... I saw a freeze saying "99% done" (ie. not
> 100%), btw.
The number is not always accurate because of rounding errors. I think we can
safely assume that it always happens after the entire image has been written.
> Are other pm_test values meaningful with s2disk? Is this
> handled explicitly in s2disk, or does simply the kernel act as if it was
> resumed instead of providing the system image after SNAPSHOT_CREATE_IMAGE?
The latter.
> > On Wednesday 11 November 2009, Ferenc Wagner wrote:
> >
> >> I already did the test for STR (see
> >> http://bugs.freedesktop.org/show_bug.cgi?id=22126#c3), but will redo
> >> with the current kernel tonight.
> >
> > OK, thanks.
>
> No change on this front, FWIW. But rc7 is out now, I'll test again.
Not sure if that's going to work, but yes please test it.
Thanks,
Rafael
next prev parent reply other threads:[~2009-11-13 19:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87fx93pwv2.fsf@tac.ki.iif.hu>
[not found] ` <200910281956.44791.rjw@sisk.pl>
[not found] ` <87d447m52t.fsf@tac.ki.iif.hu>
2009-10-29 18:36 ` [linux-pm] intermittent suspend problem again Rafael J. Wysocki
2009-10-29 22:31 ` Ferenc Wagner
2009-10-30 18:18 ` Rafael J. Wysocki
2009-10-30 19:03 ` Ferenc Wagner
2009-10-30 20:38 ` [linux-pm] " Rafael J. Wysocki
2009-10-31 12:02 ` Alan Jenkins
2009-10-31 14:06 ` Ferenc Wagner
2009-10-31 19:11 ` Rafael J. Wysocki
2009-11-01 21:53 ` Ferenc Wagner
2009-11-03 11:02 ` Ferenc Wagner
2009-11-11 11:29 ` Ferenc Wagner
2009-11-11 11:38 ` Rafael J. Wysocki
2009-11-11 13:29 ` Ferenc Wagner
2009-11-11 14:47 ` Rafael J. Wysocki
2009-11-13 16:35 ` Ferenc Wagner
2009-11-13 19:59 ` Rafael J. Wysocki [this message]
2009-11-14 1:50 ` Ferenc Wagner
2009-11-14 18:52 ` Rafael J. Wysocki
2009-11-18 1:12 ` Ferenc Wagner
2009-11-18 14:05 ` Ferenc Wagner
2009-11-18 22:13 ` Rafael J. Wysocki
2009-11-18 22:54 ` Ferenc Wagner
2009-11-19 12:00 ` Ferenc Wagner
2009-11-19 13:02 ` Ferenc Wagner
2009-11-19 19:42 ` Rafael J. Wysocki
2009-11-21 23:59 ` [linux-pm] " Ferenc Wagner
2009-11-28 19:01 ` Ferenc Wagner
2009-11-29 0:29 ` Rafael J. Wysocki
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=200911132059.46377.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=wferi@niif.hu \
--cc=yakui.zhao@intel.com \
/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