Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!rice!sun-spots-request
From: eos!jbm@eos.arc.nasa.gov (Jeffrey Mulligan)
Newsgroups: comp.sys.sun
Subject: BUSERR crashes system
Keywords: Miscellaneous
Message-ID: <1990Aug2.003020.17590@rice.edu>
Date: 1 Aug 90 17:05:54 GMT
Sender: sun-spots-request@rice.edu
Organization: Sun-Spots
Lines: 16
Approved: Sun-Spots@rice.edu
Originator: spots@titan.rice.edu
X-Sun-Spots-Digest: Volume 9, Issue 291, message 1

We have a hardware device which generates a bus error (timeout) to
indicate a certain error condition.  The vendor-supplied software uses
mmap() to map the device registers into user space, where most of the work
is done.  In this case, the bus error causes a BUSERR signal to be sent to
the user process.

For various reasons, we need certain functions to be performed in the
kernel.  Unfortunately, when the statement which causes the bus error is
executed inside of the device driver, the system panics.

Q:  Is there any way to trap and deal with this type of event inside
the kernel?

	Jeff Mulligan (jbm@eos.arc.nasa.gov)
	NASA/Ames Research Ctr., Mail Stop 262-2, Moffet Field CA, 94035
	(415) 604-3745