From owner-freebsd-hardware  Wed May 17 20:59:11 1995
Return-Path: hardware-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id UAA24011
          for hardware-outgoing; Wed, 17 May 1995 20:59:11 -0700
Received: from spice.tea.org (spice.tea.org [204.182.11.244])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA24005
          for <freebsd-hardware@FreeBSD.org>; Wed, 17 May 1995 20:59:10 -0700
Received: by spice.tea.org (8.6.9/8.6.12)
	id UAA00484; Wed, 17 May 1995 20:59:22 -0700
Date: Wed, 17 May 1995 20:59:22 -0700
From: Christopher Seiwald <seiwald@tea.org>
Message-Id: <199505180359.UAA00484@spice.tea.org>
To: freebsd-hardware@FreeBSD.org
Subject: Re: bad memory..
Sender: hardware-owner@FreeBSD.org
Precedence: bulk

> > 
> > system: 486/33 isa, aha1542, 16mb
> > 
> > added another 16mb and it went crazy with programs dumping core, and
> > kernel traps all over the place.  so i suspect the memory is bad (this
> > machine has run with 20Mb previously, and has bounce buffers configured
> > etc)..
> > 

Two comments:

1)	You might try replacing the first 16mb with the 2nd, rather than
	augmenting it, to see if your problem is due to the amount of
	memory or due to the new memory.

	If it fails with just the new memory, it could be because you
	were running at the system's margin and the new memory is just
	a tad slower than the old.

	If it fails only with both, it could be because you were running
	at the system's margin and the additional loading on the
	(memory bus) drivers slowed them down.

	People tend to doctor the voodoo BIOS parameters to get their system
	as fast as possible, only to find themselves beyond the ratings of
	their components (CPU, bus, memory) when they fully load the system.

2)	If you think program faults and panics are a drag: when my system
	was overclocked it worked fine except: when compiling the kernel,
	the cpp would complain about mangled # directives.  Go figure.
	My suspicion is that the CPU wasn't executing some sequences
	of instructions properly, but it is hard to pinpoint.

Christopher