From owner-freebsd-usb@FreeBSD.ORG Mon Jan 31 07:36:43 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 89056106564A for ; Mon, 31 Jan 2011 07:36:43 +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 150148FC0A for ; Mon, 31 Jan 2011 07:36:42 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=LfWZgthhXpRoR/5kSLoV97TeOFxNHdDd5OkOatCv3DI= c=1 sm=1 a=0Ne2ifNP0foA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=CaZGLStMKos02XLnMq4A:9 a=PlE_CEpJbul8eeFUXriQ5jb5nHwA:4 a=wPNLvfGTeEIA: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 80756777; Mon, 31 Jan 2011 08:36:40 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Mon, 31 Jan 2011 08:36:43 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.2-PRERELEASE; KDE/4.4.5; amd64; ; ) References: <812AE6D766648AFE2AE736F3@Octa64> In-Reply-To: <812AE6D766648AFE2AE736F3@Octa64> X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq,NwSZ4V" =?iso-8859-1?q?=7CLR=2E+tj=7Dg5=0A=09=25V?=,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( =?iso-8859-1?q?=0A=09=3AAuzV9=3A=2EhESm-x4h240C=609=3Dw?= MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201101310836.43402.hselasky@c2i.net> Cc: Subject: Re: FTDI Com ports "just stop" 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: Mon, 31 Jan 2011 07:36:43 -0000 On Sunday 30 January 2011 19:57:07 Karl Pielorz wrote: > Any hints how I can try and debug this? I think it might be related to the > 2nd set of 4 FTDI ports, as I didn't notice this issue for the few weeks > the system ran with just 4 ports connected. Try connecting a null-modem cable and see if you can loop any data. Also you can try a "usbconfig -d X.Y reset" --HPS