From: Ross Dickson <ross@datscreative.com.au>
To: linux-kernel@vger.kernel.org
Subject: 2.4.24 Paging Fault, Cache tries to swap with no swap partition
Date: Sun, 15 Feb 2004 03:06:35 +1000 [thread overview]
Message-ID: <200402150306.35704.ross@datscreative.com.au> (raw)
Greetings,
I have an imaging system writing files to removable hard drives.
Compact Flash boot with ram drives so I usually have no swap partition or file.
Recently I upgraded kernel from 2.4.20 to 2.4.24.
System has "mem=460M" (512M ram fitted) and starts with about
400M free. After recording for a while the Cached ram acquires all
but about 4Mb MemFree.
On a hot 38C day it started Oops'ing re paging memory. It runs the
same 2 programs all day gathering and compressing images.
Sorry I have no detail on the Oops at the moment, computer is in a vehicle and
does not normally have a screen. From memory it couldn't allocate a virtual
page.
I found if I put in a 16Mb ram drive as swap then it would grab
roughly 1.4Mb of it on occasion and keep it until recording stopped
for a while. SwapCached is either 0Kb or 1024Kb, not anything else.
Is this behaviour expected - to require a swap file?
Can the paging cache be tuned in /proc or somewhere to prevent it being so
greedy as to want more memory than the machine has?
Is the quickest fix to give it more ram. I read on another posting that with
greater than 512Mb the cache won't grab any more?
Regards
Ross.
next reply other threads:[~2004-02-14 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 17:06 Ross Dickson [this message]
2004-02-14 20:33 ` 2.4.24 Paging Fault, Cache tries to swap with no swap partition vda
2004-02-15 13:49 ` Ross Dickson
2004-02-16 10:25 ` Ross Dickson
2004-02-16 13:45 ` 2.4.24 Paging Fault, Source Line located in slab.c, kmem_cache_reap() Ross Dickson
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=200402150306.35704.ross@datscreative.com.au \
--to=ross@datscreative.com.au \
--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