From: Nigel Cunningham <ncunningham@cyclades.com>
To: Richard Mittendorfer <delist@gmx.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [swsusp] not enough memory
Date: Sat, 18 Feb 2006 10:07:58 +1000 [thread overview]
Message-ID: <200602181008.02801.ncunningham@cyclades.com> (raw)
In-Reply-To: <20060218005814.6548092d.delist@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
Hi Richard.
On Saturday 18 February 2006 09:58, Richard Mittendorfer wrote:
> Hi *,
>
> On my 64MB notebook I get the following message, when going swsusp:
>
> ..
> swsusp: Need to copy 15526 pages
> swsusp: Not enough free memory
> Error -12 suspending
> ..
>
> # free
> total used free shared buffers cached
> Mem: 62760 59884 2876 0 3828 16052
> -/+ buffers/cache: 40004 22756
> Swap: 200804 30316 170488
>
> If I end all apps but the XServer it works. I've allready added some
> more swapspace, but that didn't help. So, how much memory will I need
> for a successful suspend or better (since i can't stuff any more into
> it) is there a way to minimize the amount needed?
swsusp needs to be able to free half your memory to be able to suspend. I
don't know it intimately, but you may well be failing to do this. Being
completely biased (and not unwilling to admit it!), I'd suggest you try
Suspend2 (www.suspend2.net). It doesn't have such a limitation.
Regards,
Nigel
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-18 0:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 23:58 [swsusp] not enough memory Richard Mittendorfer
2006-02-18 0:07 ` Nigel Cunningham [this message]
2006-02-18 0:40 ` Richard Mittendorfer
2006-02-18 0:41 ` Nigel Cunningham
2006-02-18 0:57 ` Richard Mittendorfer
2006-02-18 0:57 ` Nigel Cunningham
2006-02-18 15:08 ` Pavel Machek
2006-02-18 15:11 ` Pavel Machek
2006-02-18 17:57 ` Richard Mittendorfer
2006-02-18 18:00 ` Pavel Machek
2006-05-02 3:28 ` [swsusp] not enough memory [solved with 2.6.17-rc3] Richard Mittendorfer
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=200602181008.02801.ncunningham@cyclades.com \
--to=ncunningham@cyclades.com \
--cc=delist@gmx.net \
--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