Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix-wizards
Subject: Re: cp read fault (4.2BSD on VAX 780)
Message-ID: <286@umcp-cs.UUCP>
Date: Sat, 15-Mar-86 02:48:07 EST
Article-I.D.: umcp-cs.286
Posted: Sat Mar 15 02:48:07 1986
Date-Received: Sun, 16-Mar-86 09:44:46 EST
References: <1824@brl-smoke.ARPA>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 13

In artcile <1824@brl-smoke.ARPA> kjs%tufts.csnet@csnet-relay.arpa
asks for help in tracking down a `cp read fault' machine check.

Look at the program counter (`pc') value and see in which routine
you were running.  That can be a useful clue; e.g., if you are in
dmf.c, it is probably a DMF (or of course all the access paths
all the way out to the device).  The `va/viba' register gives the
virtual address the machine was working on when it got the read
fault.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1415)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu