Path: utzoo!utgpu!water!watmath!clyde!att!chinet!bigtex!pmafire!dave
From: dave@pmafire.UUCP (Dave Remien)
Newsgroups: comp.unix.microport
Subject: Re: SysV/386: db module not cofigured ???
Summary: Info on panic dump can be useful
Keywords: Not a bug or still is it
Message-ID: <467@pmafire.UUCP>
Date: 2 Oct 88 21:53:35 GMT
References: <26061@ucbvax.BERKELEY.EDU> <835@obdient.UUCP> <431@l5comp.UUCP> <687@swivax.UUCP>
Reply-To: dave@pmafire.UUCP (Dave Remien)
Organization: WINCO, INEL, Idaho
Lines: 27

>From: betel@swivax.UUCP (Michiel Betel)
>Message-ID: <687@swivax.UUCP>

>After numerous reinstallations of sysV/386 U2.2 we got rid of an
>unexpected intterupt 0x4. This one occured at startup, gave a double Panic, 
>entered the none existant db module and hung the system after dumping
>2516 pages of core. It seems it was caused by a buggy devicedriver for
>our multiport serial board, because since I've installed the new driver
>the problem is gone.
>This error message should really be documented, because the dump of registers
>generates beautiful patterns but is not very usefull.

Various articles posted to this newsgroup (I think by John Sully of
Microport), and discussed on the Microport BBS, show how to use the
panic dump to figure out where in the kernel the panic occurred. I once
had a beta kernel Microport sent which had the debug module; you could
wander around (albeit blindly, without documentation) in the kernel and
look at things. I agree that an explanation of how to determine where
the panic was caused should be in the Sys Admin documentation.



-- 
----------
Dave Remien - WINCO Computer Engineering Group (only somewhat confused, now)
208-526-3523, 0800 to 1615 MDT; 208-524-1906, 1800 'til whenever
Potential paths: ...!bigtex!pmafire!dave | ...!ucdavis!egg-id!rzd