*BSD News Article 10769


Return to BSD News archive

Received: by minnie.vk1xwt.ampr.org with NNTP
	id AA641 ; Sat, 06 Feb 93 15:00:35 EST
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!paladin.american.edu!gatech!news.ans.net!cmcl2!sbcs.sunysb.edu!stark.UUCP!gene
From: gene@stark.uucp (Gene Stark)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] kernel on fixit-0.2 and Maxtor
Date: 3 Feb 93 19:00:27
Organization: Gene Stark's home system
Lines: 31
Distribution: world
Message-ID: <GENE.93Feb3190027@stark.stark.uucp>
References: <9301311808.AA00866@clio.iqm.unicamp.br>
	<1993Feb2.021606.25706@coe.montana.edu>
	<1993Feb3.160736.26695@cm.cf.ac.uk>
NNTP-Posting-Host: stark.uucp
In-reply-to: paul@isl.cf.ac.uk's message of 3 Feb 93 16:07:35 GMT

paul@isl.cf.ac.uk (Paul) writes:

>At the moment I'm still trying to work out why everything gets
>SIGBUS and SIGSEGV traps on my machine.
>
>Is anyone else suffering from this problem. It's impossible to rebuild
>my source tree with gcc-2.3.3 because after a few minutes the compiler
>dies from a trap and it takes a reboot to fix it.
>
>HELP!
>

I don't have this problem.  My system (486DX/33, Trident 8900C, Connor IDE
drive) is now very stable with the 0.2 patchkit, CGD's com driver, and
syscons0.1.  The system has not crashed on its own since I installed the
patchkit over a week ago.  (I did get one panic:trap when I tried pounding
on ^C during the autoboot sequence.)  I am still using the 0.1 distribution
gcc 1.39 binaries.

However, when I first bought my system last summer, I *did* have problems
such as you describe.  Someone on the net suggested it might be sub-spec
chips in the external cache, and by golly, it was!  I haven't had any trouble
after I replaced the chips with ones that met the spec in the manual for my
motherboard.  If you haven't tried it, I suggest disabling the external
cache and see what happens.

							- Gene Stark


--
							stark@cs.sunysb.edu