From: Hugh Dickins <email@example.com>
To: Martin Josefsson <firstname.lastname@example.org>
Cc: Lukas Hejtmanek <email@example.com>, <firstname.lastname@example.org>
Subject: Re: Swapoff inifinite loops on 2.6.10-bk (was: .6.10-bk8 swapoff after resume)
Date: Thu, 6 Jan 2005 22:00:09 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.email@example.com> (raw)
On Thu, 6 Jan 2005, Martin Josefsson wrote:
> On Thu, 2005-01-06 at 14:47 +0100, Lukas Hejtmanek wrote:
> > I've tried 2.6.10-bk8 suspend/resume. After resume I usually do swapoff -a to
> > load all the pages from swap to memory. Unfortunately with the latest version
> > swapoff does not work. It seems to cycle in an endless loop reading data from
> > disk.
> I second that, after resume my machine does exactly the same.
> It swaps in most of the data, but it leaves ~1700kB on the swapdevice
> that it doesn't manage to swap in, and apparently reads this over and
> over again.
> But it probably doesn't have anything to do with swsusp, I can reproduce
> it without ever having suspended, just fill up the memory so the machine
> swaps and then the same thing happens.
> Apparently kernels from -bk in late december works fine, so it's a
> recent introduction.
> Needs investigating.
Curious. I regularly check that swapoff is working (though not suspend
and resume), and have not noticed this. You fill memory so the machine
swaps, let the memory hog exit, then swapoff hangs indefinitely (not just
taking a long time)? With no suspend+resume since booting at all?
How much memory? How much swap? What .config? I'll try it tomorrow.
next prev parent reply other threads:[~2005-01-06 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 13:47 2.6.10-bk8 swapoff after resume Lukas Hejtmanek
2005-01-06 21:14 ` Swapoff inifinite loops on 2.6.10-bk (was: .6.10-bk8 swapoff after resume) Martin Josefsson
2005-01-06 22:00 ` Hugh Dickins [this message]
2005-01-07 6:53 ` Martin Josefsson
2005-01-08 16:00 ` Hugh Dickins
2005-01-08 16:23 ` Martin Josefsson
2005-01-08 19:57 ` Andrew Morton
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).