Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!uunet!usc!elroy.jpl.nasa.gov!ames!sun-barr!olivea!mintaka.lcs.mit.edu!ogicse!news.u.washington.edu!uw-beaver!cornell!cs.cornell.edu!cchase
From: cchase@cs.cornell.edu (Craig Chase)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD tip locks up
Keywords: 386BSD lockup
Message-ID: <1992Sep15.123829.12039@cs.cornell.edu>
Date: 15 Sep 92 12:38:29 GMT
References: <191hpkINN4ag@agate.berkeley.edu>
Sender: news@cs.cornell.edu (USENET news user)
Organization: Electrical Engineering, Cornell University, Ithaca NY
Lines: 41
Nntp-Posting-Host: bullwinkle.cs.cornell.edu
I've had problems with system lock-up's using both tip and kermit.
The symptoms are, I log in, type "tip com1" and blammo... deadsville.
After pressing the reset button, waiting for fsck to repair the damage
to the file system and rebooting again, I log in, type "kermit"
"set line /dev/com0" "set speed 9600" "con" and blammo... deadsville.
This does not appear to be just a process lockup, but a full fledged kernel
wedge.
Note, I don't get lockups every time, it appears to be the case that if
I am lucky enough to avoid a lockup once, I'm free from them until the next
time I reboot the machine (i.e. I can get out of tip/kermit and restart).
Anyone have similar problems?
NOTE I've had the same trouble with and without using CDG's com.c driver.
Hardware and software specifics
386BSD Rel 0.1 with minor patches (all of which have been posted to this group)
misc fs-performance patches
misc ps patches
big-mem patch
heavy-load patch
generic 486DX/33 (OPTi) 64K X-cache enabled
16Meg 70ns RAM
AH-1542B SCSI interface
Seagate 3283N 240Meg SCSI disk
ATI Wonder XL (1Meg) with mouse *disabled*
No I/O card
Zoom 14.4K faxmodem (internal) installed as com1(in PC lingo, or com0 in CDG)
--
------------------------------------------------------------------------
| Craig Chase | This space for rent |
| cchase@ee.cornell.edu | 555-8968 |
------------------------------------------------------------------------