Date: Wed, 21 Sep 2005 11:25:50 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: ticso@cicely.de Cc: freebsd-current@freebsd.org Subject: Re: serial ttys broken? Message-ID: <20050921112404.R34322@fledge.watson.org> In-Reply-To: <20050921091751.GQ552@cicely12.cicely.de> References: <20050920110023.GA468@ip.net.ua> <6136.1127217196@critter.freebsd.dk> <dgp681$o48$1@sea.gmane.org> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050921112404.R34322>