From: Richard Mittendorfer <delist@gmx.net>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [swsusp] not enough memory
Date: Sat, 18 Feb 2006 18:57:59 +0100 [thread overview]
Message-ID: <20060218185759.248208f9.delist@gmx.net> (raw)
In-Reply-To: <20060218151115.GC5658@openzaurus.ucw.cz>
Also sprach Pavel Machek <pavel@suse.cz> (Sat, 18 Feb 2006 16:11:16
+0100):
> On Sat 18-02-06 00:58:14, Richard Mittendorfer wrote:
> > 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?
>
> 128MB should be enough for you.
Swap? 128M was my first attempt -- OOM when the box was heavily loaded.
IIRC no effect on swsusp - there are 64M Ram + 2M Video + Kernel + X?.
The reason I did it were some google results talking about free pages.
There were some solutions talking about adding swap.
(Ram? Would be the way to go, but it's fully loaded.)
> Or try modifying try_to_free memory
> routine to retry shrink_all_mem few more times, with schedule() in
> between...
Uhh. I don't think this will be a good idea /me ha[ck|rm]ing good ol'
linux source. ;-)
sl ritch
next prev parent reply other threads:[~2006-02-18 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 23:58 Richard Mittendorfer
2006-02-18 0:07 ` Nigel Cunningham
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 [this message]
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=20060218185759.248208f9.delist@gmx.net \
--to=delist@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.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
all inboxes | Powered by JetHome®