Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!spool.mu.edu!news.clark.edu!netnews.nwnet.net!ns1.nodak.edu!agassiz.cas.und.NoDak.Edu!agassiz.cas.und.NoDak.Edu!rand
From: rand@cs.UND.NoDak.Edu (Douglas K. Rand)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: ed0: warning - reciever ring buffer overflow
Date: 19 Sep 1993 13:15:46 -0500
Organization: University of North Dakota, Grand Forks, ND
Lines: 24
Message-ID: <RAND.93Sep19131545@agassiz.cas.und.NoDak.Edu>
References: <RAND.93Sep17103923@agassiz.cas.und.NoDak.Edu> <g89r4222.748432320@kudu>
NNTP-Posting-Host: agassiz.cas.und.nodak.edu
To: g89r4222@kudu.ru.ac.za (Geoff Rehmet)
In-reply-to: g89r4222@kudu.ru.ac.za's message of 19 Sep 93 09:52:00 GMT
>>>>> "Rand" == Douglas K. Rand <rand@cs.und.nodak.edu>
>>>>> "Geoff" == Geoff Rehmet <g89r4222@kudu.ru.ac.za>
Rand> I've been getting a lot of these warnings:
Rand> ed0: warning - reciever ring buffer overflow
Geoff> In my experience this can happen occasionally (when you are
Geoff> loading the network heavily) and isn't really worth
Geoff> worrying about.
I probably wasn't very clear in my original post. In a span of 10
minutes I've gotten over 100 of these warnings. They almost always
happen when I'm heavily using NFS, and they even seem to cause
nfs server <host>:<mnt-point>: not responding
nfs server <host>:<mnt-point>: is alive again
messages.
--
Douglas K. Rand UND Aerospace - Scientific Computing Center
Home: +1 218 773 0120 University of North Dakota
Office: +1 701 777 2801 Box 9022, Grand Forks ND 58202-9022
Internet: rand@cs.UND.NoDak.Edu UUCP: ...!uunet!plains!agassiz!rand