public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Pringlemeir <bpringle@sympatico.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: rbultje@ronald.bitfreak.net (Ronald Bultje),
	linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: >128 MB RAM stability problems (again)
Date: 04 Jul 2001 23:16:43 -0400	[thread overview]
Message-ID: <m2sngc3w10.fsf@sympatico.ca> (raw)
In-Reply-To: <E15HsKg-0001Pk-00@the-village.bc.nu>
In-Reply-To: Alan Cox's message of "Wed, 4 Jul 2001 20:29:06 +0100 (BST)"


 >> 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

 Alan> Can I suggest you change your memory vendor and/or get an
 Alan> antistatic wrist strap ?

I also have had problems with a machine that had 128Mb + 64 Mb.  I
discovered the following about 2.4.x.  You _should_ have a swap file
that is double RAM.  Mixing different SDRAM types is probably a bad
thing.  So if you upgraded, then that might be problematic.

However, when I did have 196 Mb it completely trashed my file system.
I also work with electronic components and these were handled in an
ESD safe manner.  It may be possible to set the SDRAM controller to
handle disparate SDRAM chips...but it is probably very painful.  I
have done this on an MPC860 and a Coldfire chip.  However, I haven't
the faintest clue about PC controllers.

Perhaps when I am feeling brave again, I will return to try additional
memory.

hth,
Bill Pringlemeir.



  parent reply	other threads:[~2001-07-05  3:19 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 [this message]
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=m2sngc3w10.fsf@sympatico.ca \
    --to=bpringle@sympatico.ca \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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