From: Ronald Bultje <rbultje@ronald.bitfreak.net>
To: Chris Siebenmann <cks@utcc.utoronto.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: >128 MB RAM stability problems (again)
Date: 05 Jul 2001 10:44:25 +0200 [thread overview]
Message-ID: <994322676.768.0.camel@tux> (raw)
In-Reply-To: <01Jul4.172916edt.62972@gpu.utcc.utoronto.ca>
In-Reply-To: <01Jul4.172916edt.62972@gpu.utcc.utoronto.ca>
On 04 Jul 2001 17:29:12 -0400, Chris Siebenmann wrote:
> You write:
> | 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?
>
> Me. Two machines. (Both 2.4.5 high -ac kernels.)
>
> I strongly suggest getting memtest86 and running it on all of your
> problematic machines.
I ran memtest tonight on all machines....
It gave 0 errors on all of them.....
So.... this leads to the conclusion that the memory is okay, and that
something else must be the problem.... Could it still be a failing power
supply or something? It seems both computers have a 230 W power supply.
Might be a problem, I guess, I can buy a 400 W thingy if that makes
sense.
Other solutions I heard:
- antistatic wrist strap: already have one :-)
- BIOS fiddling... What exactly should I look for? They are, as far as I
can see, identical memory sticks, probably both from different
suppliers, but besides that quite the same....
- are there different brands of memory of different quality and might
that be a possible cause of the problems? And if so - what are good
memory brands and what are the bad ones?
- I mixed different types of SDRAM... Could be it.... My mainboard
manual is not really clear about this.... And I have no clue what brand
of memory I bought... they are all 133 MHz SDRAM sticks, some 64 MB,
some 128 MB.... MB manual says it can handle all 64/128 MB sticks...
- <your solution here :-)>
Anyway, thanks for any advice until now and thanks for listening again,
hope to hear more solutions.
--
Ronald Bultje
next parent reply other threads:[~2001-07-05 6:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01Jul4.172916edt.62972@gpu.utcc.utoronto.ca>
2001-07-05 8:44 ` Ronald Bultje [this message]
2001-07-04 20:57 ` >128 MB RAM stability problems (again) 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
2001-07-04 20:45 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
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
-- 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=994322676.768.0.camel@tux \
--to=rbultje@ronald.bitfreak.net \
--cc=cks@utcc.utoronto.ca \
--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