From owner-freebsd-bugs@FreeBSD.ORG  Wed May 27 10:02:53 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A9A35B34
 for <freebsd-bugs@FreeBSD.org>; Wed, 27 May 2015 10:02:53 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 93DB6961
 for <freebsd-bugs@FreeBSD.org>; Wed, 27 May 2015 10:02:53 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4RA2rGj027668
 for <freebsd-bugs@FreeBSD.org>; Wed, 27 May 2015 10:02:53 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 200445] login into system on serial line /dev/cuaU0 hangs on
 open of /dev/tty
Date: Wed, 27 May 2015 10:02:53 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: guru@unixarea.de
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-200445-8-3YO3U9zHrm@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200445-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-200445-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 May 2015 10:02:53 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200445

--- Comment #6 from Matthias Apitz <guru@unixarea.de> ---
(In reply to Konstantin Belousov from comment #5)

I have not specified hw flow control and I do not know if the USB-serial
supports this. As described in the handbook, I added to /etc/ttys a line:

cuaU0 "/usr/libexec/getty std.9600"    vt102    on secure

and after 'kill -HUP 1' on the terminal, login as root is possible and, for
example, an 'ls -lR /' works nicely passing the output fine to the VT102; i.e.
I do not think, that we have some flow control issue; 

the only things I have figured out so far are:

1) one can not use /bin/sh as login shell, it will hang on login;
2) you can not open /dev/tty after login; it will hang
3) if you use MUA mutt, and below this the vim to write the mail, mutt will
   hang too after the end of vim; and a Ctrl-C makes it continue (perhaps
   for the same reason of hang on /dev/tty open call)

what Do you want me to check or change exactly?
Thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.