From: Chris Wright <chrisw@osdl.org>
To: Dave Jones <davej@redhat.com>
Cc: Chris Wright <chrisw@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: kswapd in tight loop 2.6.9-rc3-bk-recent
Date: Thu, 7 Oct 2004 14:49:48 -0700 [thread overview]
Message-ID: <20041007144948.K2357@build.pdx.osdl.net> (raw)
In-Reply-To: <20041007213913.GA5302@redhat.com>; from davej@redhat.com on Thu, Oct 07, 2004 at 10:39:13PM +0100
* Dave Jones (davej@redhat.com) wrote:
> I saw the same thing yesterday, also on an amd64 box though that
> could be coincidence. The kswapd1 process was pegging the cpu at 99%
> kswapd0 was idle.
Same here.
> After a few minutes, the box became so unresponsive
> I had to reboot it.
Well, that CPU is useless ;-) Otherwise the thing is still responding.
One thing I noticed is the swap usage:
# grep Swap proc/meminfo
SwapCached: 4 kB
SwapTotal: 2031608 kB
SwapFree: 2031604 kB
So, I'm guessing the first page that went out to swap started this thing
off.
> I had put this down to me fiddling with some patches, and it hasnt'
> reappeared today yet, but it sounds like we're seeing the same thing.
I do have some local changes too. But nothing that should trigger this.
> Sadly, I didn't get a profile of what was happening.
> A 'make allmodconfig' triggered it for me, on a box with 2GB of ram,
> and 2GB of swap. No swap was in use when things 'went wierd', and
> there was a bunch of RAM sitting free too (about half a gig if memory
> serves correctly)
Memory's a bit tighter here, but still 55M free though.
# cat /proc/meminfo
MemTotal: 2053240 kB
MemFree: 55324 kB
Buffers: 161900 kB
Cached: 1321312 kB
SwapCached: 4 kB
Active: 988476 kB
Inactive: 651820 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 2053240 kB
LowFree: 55564 kB
SwapTotal: 2031608 kB
SwapFree: 2031604 kB
Dirty: 28 kB
Writeback: 0 kB
Mapped: 205600 kB
Slab: 334968 kB
Committed_AS: 581136 kB
PageTables: 8916 kB
VmallocTotal: 536870911 kB
VmallocUsed: 3080 kB
VmallocChunk: 536867727 kB
HugePages_Total: 0
HugePages_Free: 0
Hugepagesize: 2048 kB
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-10-07 21:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 21:20 kswapd in tight loop 2.6.9-rc3-bk-recent Chris Wright
2004-10-07 21:39 ` Dave Jones
2004-10-07 21:49 ` Chris Wright [this message]
2004-10-07 23:40 ` Andrew Morton
2004-10-08 0:34 ` Nick Piggin
2004-10-08 0:37 ` Andrew Morton
2004-10-08 0:51 ` Chris Wright
2004-10-08 1:40 ` Andrew Morton
2004-10-08 0:42 ` Andrew Morton
2004-10-08 1:41 ` Chris Wright
2004-10-08 1:51 ` Chris Wright
2004-10-08 1:53 ` Andrew Morton
2004-10-08 2:46 ` Nick Piggin
2004-10-08 3:01 ` Andrew Morton
2004-10-08 3:13 ` Nick Piggin
2004-10-08 3:30 ` Andrew Morton
2004-10-08 3:54 ` Nick Piggin
2004-10-08 4:48 ` Nick Piggin
2004-10-08 4:57 ` Andrew Morton
2004-10-08 5:21 ` Chris Wright
2004-10-08 5:27 ` Chris Wright
2004-10-08 10:10 ` Nick Piggin
2004-10-08 3:15 ` Nick Piggin
2004-10-08 3:05 ` Chris Wright
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=20041007144948.K2357@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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