Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!usc!cs.utexas.edu!tamsun.tamu.edu!enterpoop.mit.edu!paperboy.osf.org!brezak From: brezak@bitb.osf.org (John Brezak) Subject: 386bsd 0.1 dist crashes on install Message-ID: <1993Mar15.151935.23665@osf.org> Sender: news@osf.org (USENET News System) Organization: Open Software Foundation Date: Mon, 15 Mar 1993 15:19:35 GMT Lines: 42 -- I'm having a problem [re]installing 386bsd. I initially had 386bsd happily installed on my SCSI hard-disk after a 330MB DOS partition leaving 71MB for 386BSD. This lasted until Saturday. Then the disk would no longer fsck without panicing the kernel. It didn't matter what kernel - dist, fixit or ref's Julian's scsi. [Maybe the blizzard caused it and I can qualify for disaster relief :-)] At that point I decided after exhausting alternatives to reinstall. So I wiped out the partition and grabbed my dist disk. It booted and I typed "install". It made it through the newfs and appeared to mount the disk. But then it crashed again when it *appeared* to write to the disk. Here is the crash info if anyone have a "dist" kernel with symbols. trap type 19 code=0 eip=fe000b8c cs=8 eflags=246 cr2 8d30 cpl 0 panic: trap sigh... BTW- I tried turning off the cache and ram shadow - no difference. Here is some vital info on my setup: 386-40 8MB Adaptec 1542 SCSI Dos/Windows works fine. Ran all available diagnostics on Adaptec including BIOS based - all reports fine. Tried an init'ed disk still no luck. Maybe it is the SCSI controller ? Suggestions ? It would be nice to at least know where/how the kernel died. Can someone translate the panic to a symbol and offset so I can at least investigate. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Brezak UUCP: uunet!osf!brezak Open Software Foundation Internet: brezak@osf.org 11 Cambridge Center Fax: (617) 621 8696 Cambridge, Massachusetts Phone: (617) 621-7350