[Fwd: Re: [ale] Memory addressing failures]

[George A. Nies]

This is a multi-part message in MIME format.

--------------6553B3E321DB6DB3A8868E1
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Andy Grover wrote:

> >
> > Ran Norton NDIAGS under DOS.  Complete extended memory test (walking 1's and
> > 0's through the 32M) No failures.
> 
> This is good, I guess, but I still wouldn't cross bad memory off the
> list...
> 

I too had kernel panic problems after a memory upgrade.  I bought
memory in Jan 94.  I must have run 15 diagnostic programs, not one
of them complained.  But, boot up linux, and wham! kernel panic.  I
returned the memory to the dealer, after 1 hour of testing he found
a single bit error on one of the four chips!  I would suggest trying
just the new 16M by itself.  The box I'm on right now has 64M (I'm at
work) and it has no problems whatsoever.

	-George

--------------6553B3E321DB6DB3A8868E1
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Return-Path: ale-owner at cc.gatech.edu
Received: from anvil.gatech.edu (anvil.gatech.edu [130.207.165.41]) by mailgrunt1.mindspring.com (8.7.4/8.7.3) with ESMTP id EAA01226 for <gnies at mindspring.com>; Sun, 12 Jan 1997 04:38:36 -0500 (EST)
Received: from burdell.cc.gatech.edu (majordomo at burdell.cc.gatech.edu [130.207.3.207])
          by anvil.gatech.edu (8.8.4/8.8.4) with ESMTP
	  id EAA20066; Sun, 12 Jan 1997 04:38:28 -0500 (EST)
Received: (from majordomo at localhost) by burdell.cc.gatech.edu (8.8.4/8.6.9) id EAA04642 for ale-outgoing; Sun, 12 Jan 1997 04:34:50 -0500 (EST)
Received: from graf.cc.emory.edu (graf.cc.emory.edu [170.140.1.44]) by burdell.cc.gatech.edu (8.8.4/8.6.9) with ESMTP id EAA04630 for <ale at cc.gatech.edu>; Sun, 12 Jan 1997 04:34:44 -0500 (EST)
Received: from larry.cc.emory.edu (larry.cc.emory.edu [170.140.1.65]) by graf.cc.emory.edu (8.7.3/8.6.9-950630.01osg-itd.null) with SMTP id EAA16243; Sun, 12 Jan 1997 04:33:42 -0500 (EST)
Date: Sun, 12 Jan 1997 04:34:19 -0500 (EST)
 From: Andy Grover <agrover at emory.edu>
X-Sender: agrover at larry.cc.emory.edu
To: aesop <aesop at negia.net>
cc: ale at cc.gatech.edu
Subject: Re: [ale] Memory addressing failures
In-Reply-To: <Pine.LNX.3.91.970112000453.390A-100000 at persist.paradise.net>
Message-ID: <Pine.GSO.3.95.970112042728.8708A-100000 at larry.cc.emory.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ale at cc.gatech.edu
Precedence: bulk
X-Mozilla-Status: 0011

On Sun, 12 Jan 1997, aesop wrote:
> Hello all,
> 	I upgraded from 16M to 32M and am now having problems.  Linux 
> detects the 32M, but page faults during startup or shortly after.  The 
> kernel dump and error message are typically
<snip>

Hmm. Well, is the machine a Compaq? I understand that their BIOS is a bit
strange.

Strictly from a hardware point of view, if it's still not too much trouble
(i.e. your system's case is still not screwed on <grin>) I'd say take out
the old 16MB, and see what happens with just the new, perhaps?

> adding mem=16M eliminates any problems.

Out of curiosity, have you tried mem=18M, 20M, etc.?

> The no-hlt and no-387 boot options had no effect (suggested from a FAQ).
> 
> Ran Norton NDIAGS under DOS.  Complete extended memory test (walking 1's and 
> 0's through the 32M) No failures.

This is good, I guess, but I still wouldn't cross bad memory off the
list...

Good luck! :)

Andy


-------------------------------------------------------------------------
Andrew Grover      | "Health nuts are going to feel stupid someday, lying
agrover at emory.edu  |  in hospitals dying of nothing."   - Redd Foxx
http://www.mathcs.emory.edu/~agrover/


--------------6553B3E321DB6DB3A8868E1--