Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!labrea!aurora!ames!hc!beta!cmcl2!brl-adm!adm!narten@purdue.edu
From: narten@purdue.edu
Newsgroups: comp.unix.wizards
Subject: Re: uVAX interrupts
Message-ID: <8640@brl-adm.ARPA>
Date: Tue, 4-Aug-87 00:39:05 EDT
Article-I.D.: brl-adm.8640
Posted: Tue Aug  4 00:39:05 1987
Date-Received: Wed, 5-Aug-87 04:24:36 EDT
Sender: news@brl-adm.ARPA
Lines: 16

Art,

Thanks for the clarification. I was basing my info on the probe()
message (which reports CPU level 0x17 for all devices on the Q22), and
a USENET posting a while back. I installed a suggested fix and our
uVAX II began working. Previously, with 2 network devices, it had
crashed soon after booting.

It turns out that our ProNET card was interrupting at device level 7.
This is what caused the conflict with splimp().  Changing the
interrupt priority, and recompiling the kernel with splimp() at level
0x16 has things working fine now.

According to the DEQNA manual, it interrupts at device level 4.

Thomas