public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ronald Bultje <rbultje@ronald.bitfreak.net>
To: Peter "A." Castro <doctor@fruitbat.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: >128 MB RAM stability problems (again)
Date: 06 Jul 2001 19:55:50 +0200	[thread overview]
Message-ID: <994442162.1047.0.camel@tux> (raw)
In-Reply-To: <Pine.LNX.4.21.0107051219080.4734-100000@gremlin.fruitbat.org>
In-Reply-To: <Pine.LNX.4.21.0107051219080.4734-100000@gremlin.fruitbat.org>

Hi all,

On 05 Jul 2001 13:45:23 -0700, Peter A. Castro wrote:
> Each OS allocates the physical memory differently.  MS-Windows typically
> allocates physical memory sequentually.  Linux tends to uses both ends of
> the memory pool.  For a proper test, you need to load enough programs so
> that all of physical memory will be utilized.  Win2k may be "stable"
> because you aren't loading enough of the system to touch the second bank
> of memory.  Please try running several large programs and exercise them
> all together for several minutes.  You can use the task manager to find
> the total memory used on the system. 

Pheew (this is sarcastic)
You're fully correct, after toying a bit on win2k, I crashed it a few
times with weird errors and I must say, these blue screens in win2k look
a *lot* better than the ones I used to see in win98 ;-). They still
don't match that wonderful "kernel panic", though.

So, basically, my bios must have loaded the wrong options for my memory
which must run above it's limits which causes data corruption... Then,
my stupid question, why doesn't memtest86 detect that?

Anyway, I'll go look at the bios settings of the computers, look at the
CAS/RAS/clock timing settings like two people suggested (thanks :-) )
and hope to be happy and have a stable machine after that.

Thanks for this half-solution :-)

--
Ronald Bultje


  reply	other threads:[~2001-07-06 17:56 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
2001-07-05 17:22   ` Gary White (Network Administrator)
2001-07-05 20:45 ` Peter A. Castro
2001-07-06 17:55   ` Ronald Bultje [this message]
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=994442162.1047.0.camel@tux \
    --to=rbultje@ronald.bitfreak.net \
    --cc=doctor@fruitbat.org \
    --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