mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Mittendorfer <delist@gmx.net>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [swsusp] not enough memory
Date: Sat, 18 Feb 2006 01:40:54 +0100	[thread overview]
Message-ID: <20060218014054.15bfc4f5.delist@gmx.net> (raw)
In-Reply-To: <200602181008.02801.ncunningham@cyclades.com>

Also sprach Nigel Cunningham <ncunningham@cyclades.com> (Sat, 18 Feb
2006 10:07:58 +1000):
> Hi Richard.

Hello Nigel,
 
> On Saturday 18 February 2006 09:58, Richard Mittendorfer wrote:
> > swsusp: Need to copy 15526 pages
> > swsusp: Not enough free memory
> > Error -12 suspending
> > [...]
> 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.

Thanks for this hint. However, I'm using ck's patches and having errors 
compiling sched.c. Just took a quick look: I don't think I can get them 
working together. The  rest of the suspend2 patch (for 2.6.15.1) seems 
to apply fine to 2.6.15.4 also (Not much changes IIRC).  

> Regards,
> 
> Nigel

sl ritch

  reply	other threads:[~2006-02-18  0:41 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 [this message]
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=20060218014054.15bfc4f5.delist@gmx.net \
    --to=delist@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@cyclades.com \
    /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®