Path: utzoo!mnetor!uunet!w3vh!rolfe
From: rolfe@w3vh.UUCP (Rolfe Tessem)
Newsgroups: comp.unix.microport
Subject: Tracking down system panics.
Message-ID: <320@w3vh.UUCP>
Date: 19 Mar 88 15:45:30 GMT
Organization: W3VH Packet Radio Gateway, Great Barrington, MA
Lines: 25
Keywords: Microport System V/AT

I've been plagued by double panics lately on my System V/AT clone-based
system, and I was grateful to see John Plocher's very explicit information
on what to do with the register dump to track down the problem.  My panics
are always occurring during uucp operations, usually when on a polling job
called by cron, rather than during manual dial-up operations.  I have   
already installed the new uport serial driver from their BBS, but that has
failed to solve the problem.  The last time it happened (this morning) I
copied down the information, per John's directions, and got the following:

	cs=0x208  ip=0x5f73

Again, following the outlined procedure, I invoked vi on the system5.nm
file that was created when I made a new kernel after installing the
serial driver several weeks ago.  Searching on the pattern 02085f yielded
the following (any only) match: 02085fa2, with a corresponding symbol
description of "asysrintr".

Now, the question is, what do I do with that information to track down
my problem?

-- 
UUCP:  {uunet}!w3vh!rolfe		| Rolfe Tessem
ARPA:  w3vh!rolfe@uunet.UU.NET		| P.O. Box 793
PACKET RADIO: W3VH@WA2PVV		| Great Barrington, MA 01230
IP ADDRESS: 44.44.0.1			| (413) 528-5966