From owner-freebsd-current@FreeBSD.ORG  Thu Aug 21 16:48:16 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0EE7D1065671
	for <freebsd-current@freebsd.org>; Thu, 21 Aug 2008 16:48:16 +0000 (UTC)
	(envelope-from ed@hoeg.nl)
Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:610:652::211])
	by mx1.freebsd.org (Postfix) with ESMTP id C39E58FC12
	for <freebsd-current@freebsd.org>; Thu, 21 Aug 2008 16:48:15 +0000 (UTC)
	(envelope-from ed@hoeg.nl)
Received: by palm.hoeg.nl (Postfix, from userid 1000)
	id 2AB481CE1E; Thu, 21 Aug 2008 18:48:15 +0200 (CEST)
Date: Thu, 21 Aug 2008 18:48:15 +0200
From: Ed Schouten <ed@80386.nl>
To: Christian Weisgerber <naddy@mips.inka.de>
Message-ID: <20080821164815.GP99951@hoeg.nl>
References: <g8jufv$2vd2$1@lorvorc.mips.inka.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="OfhnfQefHcom74K3"
Content-Disposition: inline
In-Reply-To: <g8jufv$2vd2$1@lorvorc.mips.inka.de>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: uplcom broken by MPSAFE TTY commit?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Aug 2008 16:48:16 -0000


--OfhnfQefHcom74K3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello Christian,

* Christian Weisgerber <naddy@mips.inka.de> wrote:
> Has anybody noticed problems with uplcom after ed's MPSAFE TTY
> commit?
>=20
> ucom1: <FTDI USB HS Serial Converter, class 0/0, rev 1.10/2.00, addr 4> o=
n uhub2
> ucom2: <Prolific Technology Inc. USB-Serial Controller, class 0/0, rev 1.=
10/3.00, addr 5> on uhub2
>=20
> I'm seeing incomplete input followed by repetitive spew on ucom2.
> The uftdi-based ucom1 seems fine.
>=20
> ucom2 is hooked up to the serial console of an OpenBSD box.  The
> getty there issues a banner like this:
>=20
> OpenBSD/alpha (kemoauc.mips.inka.de) (tty00)
>=20
> What I now get in cu(1) is a stream of this:
>=20
> OpenBSD/alpha (kemoauc.mips.in
> OpenBSD/alpha (kemoauc.mips.in
> OpenBSD/alpha (kemoauc.mips.inka.de) (tty00)
>=20
> OpenBSD/alpha (kemoauc.mips.in
> OpenBSD/alpha (kemoauc.mips.inka.de) (tty00)
>=20
> OpenBSD/alpha (kemoauc.mips.in
> OpenBSD/alpha (kemoauc.mips.in
> OpenBSD/alpha (kemoauc.mips.inka.de) (tty00)
>=20
> OpenBSD/alpha (kemoauc.mips.in
> OpenBSD/alpha (kemoauc.mips.in
> OpenBSD/alpha (kemoauc.mips.inka.de) (tty00)
>=20
> [... and it keeps spewing ...]

I think the best thing to test first is if things work if you
enable/disable hardware and software flow control. The semantics of the
new TTY layer are pretty much the same as the old TTY layer, with the
big exception of flow control.

If that doesn't help, could you compile your kernel with USB_DEBUG,
set sysctl hw.usb.ucom.debug=3D1 and give me a dump of the text that
scrolls by?

Thanks for reporting this issue to the lists!

--=20
 Ed Schouten <ed@80386.nl>
 WWW: http://80386.nl/

--OfhnfQefHcom74K3
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAkitnE8ACgkQ52SDGA2eCwUOwQCfSs7vvbtkKio1OWhajxEeBRQ3
ZSEAn3b5YwqmiKxEZeSxatMURw1rd1pl
=hZfo
-----END PGP SIGNATURE-----

--OfhnfQefHcom74K3--