From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andy Isaacson <adi@hexapodia.org>
Cc: linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: swsusp intermittent failures in 2.6.15-rc3-mm1
Date: Thu, 1 Dec 2005 22:42:44 +0100 [thread overview]
Message-ID: <200512012242.44995.rjw@sisk.pl> (raw)
In-Reply-To: <20051201173649.GA22168@hexapodia.org>
Hi,
On Thursday, 1 of December 2005 18:36, Andy Isaacson wrote:
> My Thinkpad X40 (1.25 GB, ipw2200) has had fairly reliable swsusp since
> 2.6.13 or thereabouts, and as recently as 2.6.15-rc1-mm1 I had about 20
> successful suspend/resume cycles. But now that I'm running
> 2.6.15-rc3-mm1 I'm seeing intermittent failures like this:
Thanks a lot for the report.
The problem is apparently caused by my recent patch intended to speed up
suspend. Could you please apply the appended debug patch, try to reproduce
the problem and send full dmesg output back to me?
Rafael
Index: linux-2.6.15-rc3-mm1/kernel/power/swsusp.c
===================================================================
--- linux-2.6.15-rc3-mm1.orig/kernel/power/swsusp.c 2005-12-01 22:13:17.000000000 +0100
+++ linux-2.6.15-rc3-mm1/kernel/power/swsusp.c 2005-12-01 22:24:56.000000000 +0100
@@ -635,12 +635,18 @@
printk("Shrinking memory... ");
do {
#ifdef FAST_FREE
- tmp = count_data_pages() + count_highmem_pages();
+ tmp = count_data_pages();
+ printk("Data pages: %ld\n", tmp);
+ tmp += count_highmem_pages();
+ printk("Data and highmem pages: %ld\n", tmp);
tmp += (tmp + PBES_PER_PAGE - 1) / PBES_PER_PAGE +
PAGES_FOR_IO;
+ printk("Total pages: %ld\n", tmp);
for_each_zone (zone)
- if (!is_highmem(zone))
+ if (!is_highmem(zone)) {
tmp -= zone->free_pages;
+ printk("Pages to free: %ld\n", tmp);
+ }
if (tmp > 0) {
tmp = shrink_all_memory(SHRINK_BITE);
if (!tmp)
Index: linux-2.6.15-rc3-mm1/kernel/power/snapshot.c
===================================================================
--- linux-2.6.15-rc3-mm1.orig/kernel/power/snapshot.c 2005-12-01 22:13:58.000000000 +0100
+++ linux-2.6.15-rc3-mm1/kernel/power/snapshot.c 2005-12-01 22:39:01.000000000 +0100
@@ -437,8 +437,14 @@
static int enough_free_mem(unsigned int nr_pages)
{
- pr_debug("swsusp: available memory: %u pages\n", nr_free_pages());
- return nr_free_pages() > (nr_pages + PAGES_FOR_IO +
+ struct zone *zone;
+ unsigned int n = 0;
+
+ for_each_zone (zone)
+ if (!is_highmem(zone))
+ n += zone->free_pages;
+ printk("swsusp: available memory: %u pages\n", n);
+ return n > (nr_pages + PAGES_FOR_IO +
(nr_pages + PBES_PER_PAGE - 1) / PBES_PER_PAGE);
}
--
Beer is proof that God loves us and wants us to be happy - Benjamin Franklin
next prev parent reply other threads:[~2005-12-01 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 17:36 swsusp intermittent failures in 2.6.15-rc3-mm1 Andy Isaacson
2005-12-01 21:42 ` Rafael J. Wysocki [this message]
2005-12-02 0:55 ` Pavel Machek
2005-12-02 9:54 ` Rafael J. Wysocki
2005-12-02 18:13 ` Pavel Machek
2005-12-02 21:58 ` Rafael J. Wysocki
2005-12-03 0:21 ` Pavel Machek
2005-12-02 18:37 ` Andy Isaacson
2005-12-02 22:02 ` Rafael J. Wysocki
2005-12-02 22:54 ` Rafael J. Wysocki
2005-12-05 8:02 ` Andy Isaacson
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=200512012242.44995.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=adi@hexapodia.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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