Path: utzoo!attcan!uunet!mcvax!ukc!harrier.ukc.ac.uk!eagle.ukc.ac.uk!icdoc!qmc-cs!liam
From: liam@cs.qmc.ac.uk (William Roberts)
Newsgroups: comp.unix.aux
Subject: Re: ethernet overflow errors
Summary: It never happens to us
Keywords: Ethernet
Message-ID: <797@sequent.cs.qmc.ac.uk>
Date: 11 Jan 89 11:53:57 GMT
References: <5262@phoenix.Princeton.EDU> <ecXu9c3TV410102tQOg@amdahl.uts.amdahl.com>
Reply-To: liam@cs.qmc.ac.uk (William Roberts)
Organization: Computer Science Dept, Queen Mary College, University of London, UK.
Lines: 24
Expires:
Sender:
Followup-To:
Distribution:

In article <ecXu9c3TV410102tQOg@amdahl.uts.amdahl.com> kucharsk@uts.amdahl.com (William Kucharski) writes:
>>      ku_fastsend: if_output failed: error=70, sendpck=0, am=0
>
>We've had a similar problem at our site.  Basically, it seems A/UX can't
>deal with much Ethernet traffic.  If your Ethernet is at all heavily used,
>the system will print the first two messages and bring the Ethernet card
>off-line.

We never see this problem, and our Ethernet is fairly well
loaded (130+ machines inc Macs/Suns, lots of EtherTalk, lots of
TCP/IP, a few diskless Suns, 45 machines mounting virtually
everything from file servers via NFS, etc., etc.).
However, we are using the Kinetics EtherPort II cards,
so this may be a difference at that level (hardware/driver).

For what it's worth, ku_fastsend is probably associated with NFS
and the error=70 is a standard errno message, namely ENETDOWN,
which is what you'd expect if the driver has just turned its
toes to the sky...
-- 

William Roberts         ARPA: liam@cs.qmc.ac.uk  (gw: cs.ucl.edu)
Queen Mary College      UUCP: liam@qmc-cs.UUCP
LONDON, UK              Tel:  01-975 5250