From: Ronald Bultje <rbultje@ronald.bitfreak.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: >128 MB RAM stability problems (again)
Date: 04 Jul 2001 22:45:24 +0200 [thread overview]
Message-ID: <994279551.1116.0.camel@tux> (raw)
Hi,
you might remember an e-mail from me (two weeks ago) with my problems
where linux would not boot up or be highly instable on a machine with
256 MB RAM, while it was 100% stable with 128 MB RAM. Basically, I still
have this problem, so I am running with 128 MB RAM again.
I've been running Mandrake 7.2 on another machine for some time - no
problem, until..... I added another 64 MB RAM and tried to install
redhat (25 times (!!!)) and Mandrake 8.0... Both crash with memory
faults..... Redhat just freezes or givesa a python warning, Mandrake
gives a segfault with a warning that "memory is missing".... Both refuse
to complete installation...
I'm kind of astounded now, WHY can't linux-2.4.x run on ANY machine in
my house with more than 128 MB RAM?!? 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...)?
First machine is a Intel P-II 400 with 128 MB RAM (133 MHz SDRAM) and
crashing when I insert an additional 128 - it's running RH-7.0 with
kernel-2.4.4. Second machine is an AMD Duron 600 with 196 MB RAM (also
133 MHz SDRAM), crashing during the installation of both Mandrake 8.0
and Redhat 7.1 and which used to run stable with 128 MB RAM or 64 MB RAM
with Mandrake-7.2. Win2k runs stable on this machine in all
configurations.
I'm getting desperate.... win2k is running stable and it's scary to see
linux crash while win2k runs stable and smooth.
(ps I'm not subscribed to the list - please CC a copy to me when
replying)
Thanks in advance for any help on this,
--
Ronald Bultje
next reply other threads:[~2001-07-04 18:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-04 20:45 Ronald Bultje [this message]
2001-07-04 19:11 ` >128 MB RAM stability problems (again) 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
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=994279551.1116.0.camel@tux \
--to=rbultje@ronald.bitfreak.net \
--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