Path: utzoo!utgpu!attcan!uunet!mcvax!hp4nl!swivax!betel
From: betel@swivax.UUCP (Michiel Betel)
Newsgroups: comp.unix.microport
Subject: Re: SysV/386: db module not cofigured ???
Summary: interrupt errors
Keywords: Not a bug or still is it
Message-ID: <687@swivax.UUCP>
Date: 29 Sep 88 17:47:41 GMT
References: <26061@ucbvax.BERKELEY.EDU> <835@obdient.UUCP> <431@l5comp.UUCP>
Reply-To: michiel@cadlab1.UUCP (michiel betel)
Organization: SWI, UvA, Amsterdam
Lines: 11

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.

Michiel.