From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-pm@lists.osdl.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.21-rc5: swsusp: Not enough free memory
Date: Mon, 9 Apr 2007 22:20:09 +0200 [thread overview]
Message-ID: <200704092220.10039.rjw@sisk.pl> (raw)
In-Reply-To: <461A9D12.1060106@gmail.com>
On Monday, 9 April 2007 22:07, Jiri Slaby wrote:
> Rafael J. Wysocki napsal(a):
> > Thanks for testing.
> [...]
> > --- linux-2.6.21-rc5.orig/kernel/power/swsusp.c
> > +++ linux-2.6.21-rc5/kernel/power/swsusp.c
> > @@ -229,13 +229,13 @@ int swsusp_shrink_memory(void)
> > size += highmem_size;
> > for_each_zone (zone)
> > if (populated_zone(zone)) {
> > + tmp += snapshot_additional_pages(zone);
> > if (is_highmem(zone)) {
> > highmem_size -=
> > zone_page_state(zone, NR_FREE_PAGES);
> > } else {
> > tmp -= zone_page_state(zone, NR_FREE_PAGES);
> > tmp += zone->lowmem_reserve[ZONE_NORMAL];
> > - tmp += snapshot_additional_pages(zone);
>
> I have bad news for you :(. I thought I had unpatched kernel, but it happens
> in -rc6 too.
I guess you mean you're still seeing the 'not enough memory to suspend'
problem?
> Next, when this occurs, kernel CPU1 is not brought up and next suspend hangs
> on "Suspending consoles".
Hm, there probably is a bug in an error path. Do you use the built in swsusp
or s2disk?
Rafael
next prev parent reply other threads:[~2007-04-09 20:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 7:44 2.6.21-rc5: swsusp: Not enough free memory Jiri Slaby
2007-03-29 14:39 ` Rafael J. Wysocki
2007-03-29 14:39 ` Jiri Slaby
2007-04-01 18:17 ` Jiri Slaby
2007-04-01 19:23 ` Rafael J. Wysocki
2007-04-02 8:24 ` Jiri Slaby
2007-04-02 21:18 ` Rafael J. Wysocki
2007-04-03 7:37 ` Jiri Slaby
2007-04-03 10:50 ` Rafael J. Wysocki
2007-04-03 19:59 ` Jiri Slaby
2007-04-09 20:07 ` Jiri Slaby
2007-04-09 20:20 ` Rafael J. Wysocki [this message]
2007-04-11 7:36 ` Jiri Slaby
2007-04-11 9:55 ` Rafael J. Wysocki
2007-04-11 10:45 ` Jiri Slaby
2007-04-11 14:40 ` Rafael J. Wysocki
2007-04-11 15:02 ` Jiri Slaby
2007-04-12 21:36 ` Rafael J. Wysocki
2007-04-13 10:14 ` Jiri Slaby
2007-04-13 12:00 ` Rafael J. Wysocki
2007-04-13 12:21 ` Nigel Cunningham
2007-04-13 20:41 ` [RFD] swsusp problem: Drivers allocate much memory during suspend (was: Re: 2.6.21-rc5: swsusp: Not enough free memory) Rafael J. Wysocki
2007-04-13 21:34 ` Nigel Cunningham
2007-04-13 21:40 ` [RFD] swsusp problem: Drivers allocate much memory during suspend Chuck Ebbert
2007-04-13 22:10 ` [RFD] swsusp problem: Drivers allocate much memory during suspend (was: Re: 2.6.21-rc5: swsusp: Not enough free memory) Pavel Machek
2007-04-13 22:34 ` Nigel Cunningham
2007-04-13 22:38 ` Pavel Machek
2007-04-13 22:43 ` Nigel Cunningham
2007-04-13 22:35 ` Rafael J. Wysocki
2007-04-13 22:36 ` Nigel Cunningham
2007-04-13 22:40 ` Pavel Machek
2007-04-13 22:45 ` Nigel Cunningham
2007-04-13 22:57 ` Rafael J. Wysocki
2007-04-13 23:03 ` Nigel Cunningham
2007-04-14 9:33 ` Rafael J. Wysocki
2007-04-14 22:53 ` 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=200704092220.10039.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
/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