From owner-freebsd-bugs  Fri Aug 18 05:13:26 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id FAA18921
          for bugs-outgoing; Fri, 18 Aug 1995 05:13:26 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id FAA18901
          ; Fri, 18 Aug 1995 05:13:08 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id WAA10066; Fri, 18 Aug 1995 22:11:47 +1000
Date: Fri, 18 Aug 1995 22:11:47 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199508181211.WAA10066@godzilla.zeta.org.au>
To: freebsd-bugs@freefall.FreeBSD.org, freebsd-hackers@freefall.FreeBSD.org,
        ponds!rivers@dg-rtp.dg.com
Subject: Re: Problem with sio at high baud on 2.0.5?
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

>  It appears that when I set my baud rate to 38,400 - on a call-out
>line (i.e. /dev/cuaa1) - while the getty has the call-in line (/dev/ttyd1)
>opened at 19,200 - things gets locked up after a few minutes, and
>my only recourse is to reboot.   The program that has /dev/cuaa1
>opened gets blocked on a read.   No other program can access the
>device, and the blocking program can't be killed - you have to reboot
>to clear the device.

What is the `ps laxw' and `pstat -t' output for the two processes?

Bruce