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, 30 Oct 2009 21:38:37 +0100 [thread overview]
Message-ID: <200910302138.37938.rjw@sisk.pl> (raw)
In-Reply-To: <87k4yc3drd.fsf@tac.ki.iif.hu>
On Friday 30 October 2009, Ferenc Wagner wrote:
> "Rafael J. Wysocki" <rjw@sisk.pl> writes:
>
> > On Thursday 29 October 2009, Ferenc Wagner wrote:
> >
> >> "Rafael J. Wysocki" <rjw@sisk.pl> writes:
> >>
> >>> Which part of it is getting slower? Saving the image, suspending
> >>> devices or the entire hibernation overall?
> >>
> >> "Snapshotting system" before saving the image
> >
> > That may be a result of changing the way in which image memory is reserved.
> > How much memory is there in your machine?
>
> 512 MB.
So it's likely the slowdown results from the memory management rework.
Hopefully, it'll improve in the future.
> >> and saving the image as well. If s2disk didn't report funny huge negative
> >> ratios all the time,
> >
> > Hmm. This looks like a bug in s2disk.
>
> Definitely. Do you also experience this?
Not really, but I use newer versions.
> Probably an easy one, but I've never had the chance to check the CVS version
> (running 0.7 at the moment). I can probably give 0.8 a spin if you deem
> necessary. I always thought it wasn't more than a cosmetic flaw.
It probably is. You can try the current version from my git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/suspend-utils.git
Thanks,
Rafael
next prev parent reply other threads:[~2009-10-30 20:36 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 ` Rafael J. Wysocki [this message]
2009-10-31 12:02 ` [linux-pm] " 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
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=200910302138.37938.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