Path: utzoo!attcan!uunet!husc6!rice!sun-spots-request
From: smb@arpa.att.com
Newsgroups: comp.sys.sun
Subject: Re: zs3: silo overflow crashes
Keywords: Hardware
Message-ID: <8905170335.AA08340@hector.homer.nj.att.com>
Date: 17 May 89 03:35:49 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 9
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 7, Issue 298, message 3 of 18

Your machine isn't crashing because of a silo overflow, it's getting some
sort of bus error or other internal trap.  While it's printing the panic
and traceback stuff, the input silo -- from the mouse? dunno -- has filled
up and overflowed because interrupts are disabled.  When it finally has
the leisure to look at the i/o ports, while trying to sync the disks, it
notices the async i/o error and reports it.  That's pure cascade, and the
message itself is not relevant.

I don't know, though, why it's talking about zs3.