From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: swsusp fails short on memory
Date: Wed, 26 May 2004 16:35:35 +0200 [thread overview]
Message-ID: <1085582116.1785.6.camel@teapot.felipe-alfaro.com> (raw)
Hello,
I'm somewhat ignorant on the inner workings of swsusp. I have a 256MB
laptop machine running 2.6.7-rc1-bk2 + ACPI + swsusp two swap
partitions, a 256MB swap partition on /dev/hda4 plus another 256MB swap
on /dev/hda5. When trying to hibernate to disk, swsusp fails with the
following error message:
PCMCIA: socket cf71302c: *** DANGER *** unable to remove socket power
Stopping tasks:
====================================================================|
Freeing memory: ..|
/critical section: counting pages to copy.[nosave pfn
0x2f2]...............................................................
(pages needed: 46305+512=46817 free: 19214)
Suspend Machine: Couldn't get enough free pages, on 27603 pages short
Suspend Machine: Suspend failed, trying to recover...
Fixing swap signatures... ok
Restarting tasks...<4>atkbd.c: Unknown key released (translated set 2,
code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
done
What I can't unserstand is how swsusp fails with "couldn't get enough
free pages". cat /proc/swaps tells:
Filename Type Size Used Priority
/dev/hda4 partition 281128 0 0
/dev/hda5 partition 281096 192 1
What going on here? Why does swsusp fail when there is plenty of free
swap space?
NOTE: The same happens while only using a big, 512MB swap partition.
Thanks.
next reply other threads:[~2004-05-26 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 14:35 Felipe Alfaro Solana [this message]
2004-05-26 22:38 ` Nigel Cunningham
2004-05-27 19:36 ` Pavel Machek
2004-05-31 15:34 ` Felipe Alfaro Solana
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=1085582116.1785.6.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®