From: Mark Gross <mgross@linux.jf.intel.com>
To: Pavel Machek <pavel@ucw.cz>, Mark Gross <mgross@linux.jf.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: swsusp "not enough swap space" 2.6.5-mm6.
Date: Wed, 9 Jun 2004 08:32:04 -0700 [thread overview]
Message-ID: <200406090832.04064.mgross@linux.intel.com> (raw)
In-Reply-To: <20040608230450.GA13916@elf.ucw.cz>
On Tuesday 08 June 2004 16:04, Pavel Machek wrote:
> Hi!
>
> > I'm sorry for not having more information, but the failing computer is my
> > home laptop (I'll get more details after work or I'll bring it in
> > tomorrow for more details).
> >
> > Anyway, this thing does software suspend using the 2.6.2-mm1 kernel, and
> > last night I was updating it to 2.6.5-mm6, and I started getting these
> > not enough disk space errors.
> >
> > I found your bug fix patch,
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=107806008626357&w=2
> > and checked that it is included in the 2.6.5-mm6 kernel I'm using.
> >
> > Without more information does this problem ring any bells?
> >
> > Can you recommend a "good" kernel version that does reliable swsusp?
>
> Get 2.6.6, and set swappiness to 100.
>
> Pavel
2.6.6 still fails, just like the failure reported by the thread independent of
swappiness:
http://marc.theaimsgroup.com/?t=107806010900002&r=1&w=2
However; as hinted in the thread turning off premption does seem to fix the
problem.
When will the CONFIG_PREEMPT work with swsusp again? (it works with 2.6.2-mm1
on my system a NEC VERSA E120 Daylite with 512MB ram)
Also, why does it burp out such a bogus message? not enough swap, when its
trying to dump only 7000 some pages to a 700MB swap partiion that isn't used
yet is missleading.
--mgross
next prev parent reply other threads:[~2004-06-09 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 15:29 swsusp "not enough swap space" 2.6.5-mm6 Mark Gross
2004-06-08 23:04 ` Pavel Machek
2004-06-09 15:32 ` Mark Gross [this message]
2004-06-09 16:27 ` Mark Gross
2004-06-09 19:48 ` Felipe Alfaro Solana
2004-06-09 21:28 ` Mark Gross
2004-06-09 21:13 ` Pavel Machek
2004-06-09 21:00 ` 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=200406090832.04064.mgross@linux.intel.com \
--to=mgross@linux.jf.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.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