From owner-freebsd-current@FreeBSD.ORG Wed Sep 21 10:25:51 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9E7316A41F for ; Wed, 21 Sep 2005 10:25:51 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76D8C43D46 for ; Wed, 21 Sep 2005 10:25:51 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 006F746B82; Wed, 21 Sep 2005 06:25:51 -0400 (EDT) Date: Wed, 21 Sep 2005 11:25:50 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: ticso@cicely.de In-Reply-To: <20050921091751.GQ552@cicely12.cicely.de> Message-ID: <20050921112404.R34322@fledge.watson.org> References: <20050920110023.GA468@ip.net.ua> <6136.1127217196@critter.freebsd.dk> <20050920153044.GC468@ip.net.ua> <1127230793.30479.24.camel@buffy.york.ac.uk> <20050920172635.GA2811@ip.net.ua> <1127238519.30479.35.camel@buffy.york.ac.uk> <20050921091751.GQ552@cicely12.cicely.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: serial ttys broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2005 10:25:51 -0000 On Wed, 21 Sep 2005, Bernd Walter wrote: >> FreeBSD/i386 (buffy.york.ac.uk) (ttyd0) >> >> login: CCeeBSD/i386 (buffy.york.ac.uk) (ttyd0) >> >> login: >> >> Yes. >> >> And that's with ttyd0, not cuaa0, and a Windows machine at the far end >> of a 9600 baud link. A configuration which I'm pretty sure should >> perform better. No matter how hard I try, I can't manage to reproduce >> the corruption once logged in, unless I explicitly run >> /usr/libexec/getty from the shell, in which case the corruption is even >> worse: FWIW, I've been seeing this problem for ages, but have always considered it entertaining as something of a Stargate fan. I typically see just one character corruption in the common case: CreeBSD/i386 (whatever.whomever) (ttyd0) login: However, my theory has been that we have a problem when we reset serial ports on last close. I.e., just before getty is respawned and launches login. Cree, Robert N M Watson