From owner-freebsd-current  Sat May 31 01:17:28 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA12968
          for current-outgoing; Sat, 31 May 1997 01:17:28 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA12963
          for <current@FreeBSD.ORG>; Sat, 31 May 1997 01:17:19 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id SAA06707; Sat, 31 May 1997 18:12:24 +1000
Date: Sat, 31 May 1997 18:12:24 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199705310812.SAA06707@godzilla.zeta.org.au>
To: bruce@zuhause.mn.org, jmz@cabri.obs-besancon.fr
Subject: Re: sio.c: incorrect identification of 16550A
Cc: current@FreeBSD.ORG
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>In addition to this new bug, I've been seeing a problem where my
>dialout uucp's on sio1 are able to call up and log in to the remote
>system, but lock up the port without ever transmitting any data after
>completing the uucico log-in.  This has been occurring ever since the
>sio changes last week, but only when I get the following messages:
>  sio0: 64 events for device with no tp
>  sio1: 65 events for device with no tp

These are harmless.  All that matters is that the detected transmitter
fifo size is <= the actual size.  Since the detection code at best
detects the _receiver_ fifo size, there may be problems.

Bruce