Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site wlcrjs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!wlcrjs!djc
From: djc@wlcrjs.UUCP (David J. Carpenter)
Newsgroups: net.micro.att
Subject: Continuing ports WARNINGS on 3b2
Message-ID: <133@wlcrjs.UUCP>
Date: Sat, 17-Aug-85 20:51:22 EDT
Article-I.D.: wlcrjs.133
Posted: Sat Aug 17 20:51:22 1985
Date-Received: Tue, 20-Aug-85 22:05:55 EDT
Reply-To: djc@wlcrjs.UUCP (David J. Carpenter)
Organization: chinet, Public Access UN*X, Chicago
Lines: 17
Keywords: error ports 3b2

I often get the error message:
	WARNING: Express Queue Overload, One entry lost
on our 3b2.  THe manual says that this is coming from the ports board
and if it happens often, we should call a service rep and all that, but
doesn't explain the cause.  It used to happen whenever a certain terminal
was powered down.  The READY (Carrier detect to the terminal) line from UNIX
would oscillate as getty kept respawning, and eventually INIT would catch on
and shut down that line.  But now it happens sometimes when people log off,
or unplug their terminal data cables.  It seems to happen on both ports boards.
Sometime a line will get "hung" and only a reboot cures it.  One time 
a user turned off the terminal without logging off and there was a process
running on that line that couldn't be killed.
	All in all, the boards don't seem to be very reliable.  Anyone
know why this is happening?
				Thanks, 
				David Carpenter
			..!ihnp4!wlcrjs!djc