Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!uunet!haven.umd.edu!darwin.sura.net!Sirius.dfn.de!chx400!bernina!torda
From: torda@igc.ethz.ch (Andrew Torda)
Subject: Fixed: Runs at 8MHz, Crashes at 33MHz, 386bsd
Message-ID: <1992Sep8.070731.21159@bernina.ethz.ch>
Summary: buy faster memory
Sender: news@bernina.ethz.ch (USENET News System)
Organization: Computational Chemistry, ETH, Zuerich
Date: Tue, 8 Sep 1992 07:07:31 GMT
Lines: 41
Some time ago, I complained with the following problem:
At 8 MHz, my machine appears perfectly stable.
At 33 MHz, I get repeated trap type 12 panics.
What can be dependent on timing like this ?
If there are any suggestions as to where I can insert
debugging lines ?
I am not sure if this particular panic (trap type 12) holds all
the answers. The machine (at 33 MHz) has often done a
crash/reboot and wiped the errors off the screen.
Machine details:
386 clone (Blackship), no maths chip, 8M memory
ATI motherboard (ATI-386/B2-33, 64K cache)
AMI BIOS (04/09/90)
video: ET4000 based, DFI VG-5000 with 1 Mb
pc0 <color> at 0x60 irq1 on isa
com1 at 0x3f8 irq4 on isa
com2 at 0x2f8 irq3 on isa
wd0 (MAXTOR LXT-213A> at 0x1f0 irq 14 on isa
fd0 drives 0:1.2M, 1: 1.44M at 0x3f0 irq 6 drq2 on isa
The most concrete suggestions were to either add wait states or buy
faster memory. Couldn't add any more wait states, but I managed to
swap 8Mb of 80ns simms for 70 ns simms.
Instantly, I could rebuild kernels or run my little crash program
which simply allocated ever increasing amounts of memory and scribbled
through it.
The peculiarity is that with the old memory, I had been able to run
dos, windows in enhanced mode and even SCO unix.
It would still be nice to know what the cause is and why 386bsd
provokes the problem.
Thanks to several, especially forsyth@minster.york.ac.uk
-Andrew
--
Andrew Torda, Computational Chemistry, ETH, Zurich, torda@igc.ethz.ch