From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Kevin Fenzi <kevin-linux-kernel@scrye.com>, Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9-rc2-mm1 swsusp bug report.
Date: Sat, 25 Sep 2004 09:40:17 +1000 [thread overview]
Message-ID: <1096069216.3591.16.camel@desktop.cunninghams> (raw)
In-Reply-To: <20040924210958.A3C5AA2073@voldemort.scrye.com>
Hi.
On Sat, 2004-09-25 at 07:09, Kevin Fenzi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> >>>>> "Pavel" == Pavel Machek <pavel@ucw.cz> writes:
>
> Pavel> Hi!
> >> Was trying to swsusp my 2.6.9-rc2-mm1 laptop tonight. It churned
> >> for a while, but didn't hibernate. Here are the messages.
> >>
> >> ....................................................................................................
> >> .........................swsusp: Need to copy 34850 pages Sep 23
> >> 16:53:37 voldemort kernel: hibernate: page allocation
> >> failure. order:8, mode:0x120 Sep 23 16:53:37 voldemort kernel:
> Pavel> Out of memory... Try again with less loaded system.
>
> The system was no more loaded than usual. I have 1GB memory and 4GB of
> swap defined. I almost never touch swap. It might have been 100mb into
> the 4Gb of swap when this happened.
>
> What would cause it to be out of memory?
> swsup needs to be reliable... rebooting when you are using your memory
> kinda defeats the purpose of swsusp.
The problem isn't really that you're out of memory. Rather, the memory
is so fragmented that swsusp is unable to get an order 8 allocation in
which to store its metadata. There isn't really anything you can do to
avoid this issue apart from eating memory (which swsusp is doing
anyway).
Regards,
Nigel
next prev parent reply other threads:[~2004-09-24 23:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 2:19 2.6.9-rc2-mm1 swsusp bug report Kevin Fenzi
2004-09-24 14:37 ` Pavel Machek
2004-09-24 21:09 ` Kevin Fenzi
2004-09-24 23:40 ` Nigel Cunningham [this message]
2004-09-25 1:45 ` Kevin Fenzi
2004-09-25 11:53 ` Nigel Cunningham
2004-09-25 12:22 ` Nick Piggin
2004-09-25 12:56 ` William Lee Irwin III
2004-09-25 13:21 ` Nigel Cunningham
2004-09-25 12:56 ` Nigel Cunningham
2004-09-25 13:38 ` Nick Piggin
2004-09-25 13:03 ` Nigel Cunningham
2004-09-25 15:45 ` Pavel Machek
2004-09-25 22:03 ` Nigel Cunningham
2004-09-26 10:04 ` Pavel Machek
2004-09-26 21:59 ` Nigel Cunningham
2004-09-26 22:43 ` Pavel Machek
2004-09-27 10:12 ` Nigel Cunningham
2004-09-26 16:18 ` Marcelo Tosatti
2004-09-26 18:39 ` Pavel Machek
2004-09-25 10:15 ` Pavel Machek
[not found] <2HO0C-4xh-29@gated-at.bofh.it>
[not found] ` <2I5b2-88s-15@gated-at.bofh.it>
[not found] ` <2I5E5-6h-19@gated-at.bofh.it>
[not found] ` <2I7Zd-1TK-11@gated-at.bofh.it>
2004-09-25 1:05 ` Pascal Schmidt
2004-09-25 10:16 ` Pavel Machek
2004-10-10 18:17 ` Jan Rychter
2004-10-11 13:32 ` Pavel Machek
2004-10-11 14:53 ` Jan Rychter
2004-10-17 19:10 ` Pavel Machek
2004-10-17 21:40 ` Nigel Cunningham
2004-10-11 9:56 ` Stefan Seyfried
2004-10-11 14:59 ` Pavel Machek
2004-10-11 17:18 ` Stefan Seyfried
2004-10-11 19:58 ` Rafael J. Wysocki
2004-10-12 8:55 ` Pavel Machek
2004-10-13 17: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=1096069216.3591.16.camel@desktop.cunninghams \
--to=ncunningham@linuxmail.org \
--cc=kevin-linux-kernel@scrye.com \
--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