Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:1720 comp.os.386bsd.bugs:517 Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!agate!ames!cae780!bkp From: bkp@csi.com (Brian K. Pheiffer) Subject: silo overflows and failed fixes -- trying syscons-0.2 and trap 12 Message-ID: <1993Apr18.202524.12821@csi.com> Keywords: syscons-0.2,CGD,com-beta.0.2.1,silo overflow Organization: Comdisco Systems Inc., Foster City, CA Date: Sun, 18 Apr 1993 20:25:24 GMT Lines: 30 I've been running a 486DX (with patch level 0.2.2, Orchid Prodesigner IIs, 3com 3c503 at 0xDC000, com1, com2, com4 at irq 5, 32Mb, Maxtor IDE 230 Mb) with no problem except silo overflows. I've been trying different ways to fix this problem but keep hitting a wall. I first tried Gene Stark's mods to CGD's comkit. This booted and worked fine except I wasn't able to use my com ports *at all*. Every command (tip,cu,kermit) would hang trying to open the port. I saw that his was based on patchkit 0.2.2 + syscons-0.2 so I tried installing syscons-0.2. I rebuilt the kernel and right before the fsck check on reboot -- the kernel paniced with: | trap type 12 code = fe010002 eip = fe0103d5 cs = 8 eflags = 10206 \ | cr2 2726148 cpl 4040 | panic: trap | hit reset please So that wasn't optimal. I also tried CGD's com-beta.0.2.1 patches, but they also had the same problem as Stark's: I couldn't open the devices. I'm fairly sure the source tree was clean before trying each of these three senarios since I rebuild a plain kernel between each. All I'm trying to do is fix the com port silo overflow problem. Any suggestions on which approach or what I could try next? Brian Pheiffer bkp@csi.com