*BSD News Article 87596


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!solace!nntp.uio.no!newsfeeds.sol.net!hunter.premier.net!news.mathworks.com!howland.erols.net!vixen.cso.uiuc.edu!news.indiana.edu!news
From: jfieber@fallout.campusview.indiana.edu (John Fieber)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Bus Error
Date: 28 Jan 1997 03:05:08 GMT
Organization: Indiana University, Bloomington
Lines: 30
Message-ID: <5cjqd4$95a@dismay.ucs.indiana.edu>
References: <32E8B00E.346A@sh.cvut.cz> <5cj26s$mau@ns.qnis.net>
NNTP-Posting-Host: fallout.campusview.indiana.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.8
To: J.Klaus@sh.cvut.cz
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:34581

In article <5cj26s$mau@ns.qnis.net>,
	phil@ns.qnis.net (Phil Jensen) writes:
> In article <32E8B00E.346A@sh.cvut.cz>,
> Jaroslav Klaus  <J.Klaus@sh.cvut.cz> wrote:
>>The 2.1.6(5)-RELEASE very often gives me "Bus Error - core dumped"
>>message.
>>Also the cc compiler in the 2.2-BETA (APLHA) is being killed by signals
>>11 or 10.
>>I think it's similar problem. Could anybody help me?
> 
> Jarda,
> Try turning your external cache off in your BIOS.  I'm observed this
> problem several times with the external cache on.  Disabling it 
> usually does the trick. 

If turning of the cache solves the problem, then also check for any
"memory remapping" options in BIOS and turn them off if they are on,
then try re-enabling the cache.

What happens is that the area of memory used by BIOS (between
640k-1MB) gets remapped somewhere else where it can be used. 
However, your system may not be able to use it correctly.  In my
system, for example, the maximum installable RAM is 32 megabytes. 
With 32 megabytes installed and remapping enabled, this turns into 32
megabytes plus a little more. It just so happens that the external
cache gets terribly confused by that extra little bit!  I was able to
eleminate the symptom by turning off the cache, but it took me quite
a bit longer to figure out the real cause.  

-john