Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: DEC DEUNA interface
Message-ID: <8010@mimsy.UUCP>
Date: Tue, 18-Aug-87 00:42:49 EDT
Article-I.D.: mimsy.8010
Posted: Tue Aug 18 00:42:49 1987
Date-Received: Wed, 19-Aug-87 04:30:32 EDT
References: <8821@brl-adm.ARPA>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 16

In article <8821@brl-adm.ARPA> cpw%sneezy@lanl.gov (C. Philip Wood) writes:
>... doing fine except for the 'de0' which when asked to send a packet
>would return the ENOBUFS error.  The ifqueue for this device was full.
>It stayed in this state, while the other devices continued to function.

I have seen this too, though only on a Vax 8600.  I now suspect a
hardware problem, possibly like the carry chain timing problem in
785s, in the Unibus/DW780/SBIA/Abus logic chain dealing with
interrupts, as this 8600 also loses interrupts on its UDA50s (it
has two at present; both lose interrupts under heavy massbuss and
ethernet interrupt load).  The same DEUNA and one other one have
been working well on two Vax 8250s (for all of four days on one,
and about 2 weeks on the other).
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	seismo!mimsy!chris