public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Don Krause" <dkrause@optivus.com>
To: "'Ronald Bultje'" <rbultje@ronald.bitfreak.net>,
	"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: RE: >128 MB RAM stability problems (again)
Date: Thu, 5 Jul 2001 08:51:47 -0700	[thread overview]
Message-ID: <036e01c1056a$665b0d40$6cc8c58f@satoy> (raw)
In-Reply-To: <994279551.1116.0.camel@tux>

> Can someone please
> point out to me
> that he's actually running kernel-2.4.x on a machine with
> more than 128
> MB RAM and that he's NOT having severe stability problems?
> And can that same person PLEASE point out to me why 2.4.x is
> crashing on
> me (or help me to find out...)?

%uname -a
Linux cartman 2.4.0-64GB-SMP #1 SMP Wed Jan 24 15:52:30 GMT 2001 i686
unknown
%uptime
 8:35am  up 57 days, 12:42,  2 users,  load average: 2.00, 2.00, 2.00
%free
             total      used      free      shared      buffers      cached
Mem:        254904    251968      2936           0        92224       45028
-/+ buffers/cache:    114716    140188
Swap:       524656     14192    510464


Could this be a 2.4 swap issue. You NEED at least RAM x2 swap. If you're
just adding memory to
a box that's stable with 128 megs and possibly 256 megs swap (you don't
state, just guessing..)
you've now got too little swap, and boom, stability goes bye-bye.

Just haven't seen the swap issue mentioned this thread...

=Don=


  parent reply	other threads:[~2001-07-05 15:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-04 20:45 >128 MB RAM stability problems (again) Ronald Bultje
2001-07-04 19:11 ` J Sloan
2001-07-04 19:20 ` Charles Cazabon
2001-07-04 19:29 ` Alan Cox
2001-07-04 19:47   ` William Scott Lockwood III
2001-07-05  3:16   ` Bill Pringlemeir
2001-07-05  6:37     ` Ragnar Hojland Espinosa
2001-07-05 15:38       ` Bill Pringlemeir
2001-07-04 19:44 ` mark
2001-07-04 20:01 ` Jeffrey W. Baker
2001-07-04 20:05 ` George Bonser
2001-07-04 22:11 ` D. Stimits
2001-07-04 23:47 ` Peter Bornemann
2001-07-05  1:22   ` Reza Roboubi
2001-07-05  1:43     ` Charles Cazabon
2001-07-05  1:58     ` George Bonser
2001-07-05 15:51 ` Don Krause [this message]
2001-07-05 17:22   ` Gary White (Network Administrator)
2001-07-05 20:45 ` Peter A. Castro
2001-07-06 17:55   ` Ronald Bultje
2001-07-09 14:24     ` Andreas Bombe
     [not found] <01Jul4.172916edt.62972@gpu.utcc.utoronto.ca>
2001-07-05  8:44 ` Ronald Bultje
2001-07-04 20:57   ` Chris Bacott
2001-07-05  7:22   ` StarTux
2001-07-05  8:40   ` Reza Roboubi
2001-07-05 10:50     ` Ronald Bultje
2001-07-05 15:41       ` Reza Roboubi
2001-07-05  9:15   ` D. Stimits
  -- strict thread matches above, loose matches on Subject: below --
2001-07-04 20:06 Alessandro Motter Ren
2001-07-04 20:16 ` George Bonser
2001-07-04 20:52 ` Ronald Bultje

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='036e01c1056a$665b0d40$6cc8c58f@satoy' \
    --to=dkrause@optivus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rbultje@ronald.bitfreak.net \
    /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