Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!labrea!jade!ucbvax!PRISM.CLEMSON.EDU!WARNOCK
From: WARNOCK@PRISM.CLEMSON.EDU (Todd Warnock)
Newsgroups: comp.os.vms
Subject: interrupts caused by a faulty device (hardware)
Message-ID: <8709181921.AA15917@ucbvax.Berkeley.EDU>
Date: Thu, 17-Sep-87 10:17:00 EDT
Article-I.D.: ucbvax.8709181921.AA15917
Posted: Thu Sep 17 10:17:00 1987
Date-Received: Sun, 20-Sep-87 03:58:40 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 16

Is there anyway, perhaps using SDA, to determine if a piece of hardware
is generating an excessive amount of interrupts ?  The device in question
is a TM03 (recently replace) on a TU77 tape drive.  Shortly after the
TM03 was replace, the system began spending 60-70% of the CPU time on
the Interrupt stack.  No device errors were being logged (via SHOW ERROR).
A reboot termporarily(?) cleared the problem, but it's bound to come back.
Suggestions and/or other possible causes to the excessive interrupt time
would be appreciated.

Todd Warnock
VAX Systems
Clemson University
Clemson, South Carolina 29634-2803

ARPA:	Warnock@Prism.Clemson.EDU
BITnet:	Warnock@Clemson