public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Shaun Jackman <sjackman@shaw.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: swsusp list
Date: Mon, 4 Mar 2002 19:35:58 +0100	[thread overview]
Message-ID: <20020304183558.GA4117@elf.ucw.cz> (raw)
In-Reply-To: <E16gLkD-0000KR-00@quince.jackman> <20020228094035.GB4760@atrey.karlin.mff.cuni.cz> <E16gwHa-0000B7-00@quince.jackman>
In-Reply-To: <E16gwHa-0000B7-00@quince.jackman>

Hi!

> > You have to have just one swap partition. Disable one of them.
> Ok, I did that. Now I'm getting an error there's not enough swap space 
> (logical enough I think).
> 
> /critical section: Counting pages to copy[nosave] (pages needed
> :18062+152=18574 free 14689)
> Couldn't get enough free pages, on 3885 pages short.
> Kernel panic: Not enough free pages
> 
> If both swap partitions is disallowed, and one swap partition isn't enough 
> space, is there anything I can do now to make this work? I'd really
> like to 

This is not enough RAM, there's enough swap. You may try quitting some
applications.

> get suspend working.
> I know at one point 128MB was the limit on a swap partition. Is this limit 
> gone now?

Yep.

> How technically difficult is it to make swsusp work with multiple swap 
> partitions?

Should not be that hard. But you'd have to pass both partitions on
command line, etc.
								Pavel
-- 
(about SSSCA) "I don't say this lightly.  However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa

  reply	other threads:[~2002-03-04 23:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E16gLkD-0000KR-00@quince.jackman>
     [not found] ` <20020228094035.GB4760@atrey.karlin.mff.cuni.cz>
2002-03-01 23:17   ` swsusp list Shaun Jackman
2002-03-04 18:35     ` Pavel Machek [this message]
2002-03-03 23:33   ` swsusp: Unable to find swap-space signature Shaun Jackman
2002-03-07 19:31     ` Pavel Machek

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=20020304183558.GA4117@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sjackman@shaw.ca \
    /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