From owner-freebsd-usb@FreeBSD.ORG Wed Jul 6 19:37:11 2011 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77C46106564A; Wed, 6 Jul 2011 19:37:11 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.c2i.net [212.247.154.162]) by mx1.freebsd.org (Postfix) with ESMTP id CE25E8FC08; Wed, 6 Jul 2011 19:37:10 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=XR4AdwVFe5G+K9PtySS1/JOnv6WK/hruile8wX/SUjk= c=1 sm=1 a=SvYTsOw2Z4kA:10 a=noogV_DfA68A:10 a=WQU8e4WWZSUA:10 a=Q9fys5e9bTEA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=cP3mkn6HxrtQqLMeje8A:9 a=PUjeQqilurYA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe06.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 148679883; Wed, 06 Jul 2011 21:37:08 +0200 From: Hans Petter Selasky To: Renato Tambellini Date: Wed, 6 Jul 2011 21:35:18 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <201107050037.p650bnQK060628@red.freebsd.org> <201107060859.58243.hselasky@c2i.net> In-Reply-To: X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201107062135.19031.hselasky@c2i.net> Cc: freebsd-gnats-submit@freebsd.org, freebsd-usb@freebsd.org Subject: Re: usb/158650: uplcom USB To COM Device doesn't transmit data, only receive X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2011 19:37:11 -0000 On Wednesday 06 July 2011 17:37:53 Renato Tambellini wrote: > Hi Hans, > > Follow the logs of my application and cu(1) trying to access my > another BSD machine. > > The files .dump are stdout of usbdump and .log are the logs of debug from > cons. > > In cu, I get the "login: " and a write error when I try to send the > chars to the remote console: > > # cu -l /dev/ttyU0 > Connected > ]Jj > > login: write: Device not configured > write: Device not configured > ... > > The kernel reconnects the device on error and the speed are set > correctly, 19200 for my app and 9600 to access the remote console from > cu. > Hi, What are the values of the following sysctls? sysctl hw.usb.ucom.cons_unit sysctl hw.usb.ucom.cons_baud Could you set: sysctl hw.usb.ucom.debug=15 Then type something on the cu terminal and see if you get something through. I have an uplcom adapter here and I cannot reproduce except if I do the following: cu -l /dev/cuaU0 Unplug uplcom. Then type something: cu -l /dev/cuaU0 Connected write: Device not configured write: Device not configured Then I need to "killall -KILL cu" to get back to normal. NOTE: If applications opening a USB TTY device does not close on error, then the USB stack will wait until that happens before it can enumerate more devices. This is a TTY stack problem. You can try to remove the force_short_xfer=1 flag in sys/dev/usb/serial/uplcom.c for the BULK TX transfer. I'm not sure if it helps. Really strange if your uplcom crashes on a ZLP! --HPS