From owner-freebsd-usb@FreeBSD.ORG Sun Jan 30 19:06:39 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 082A3106564A for ; Sun, 30 Jan 2011 19:06:39 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 94EB48FC08 for ; Sun, 30 Jan 2011 19:06:38 +0000 (UTC) Received: from Octa64 (octa64.tdx.co.uk [62.13.130.232]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/Kp) with ESMTP id p0UIuE7A043505 for ; Sun, 30 Jan 2011 18:56:14 GMT Date: Sun, 30 Jan 2011 18:57:07 +0000 From: Karl Pielorz To: freebsd-usb@freebsd.org Message-ID: <812AE6D766648AFE2AE736F3@Octa64> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: 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: Sun, 30 Jan 2011 19:06:39 -0000 Hi, Attempting to save electricity here I've recently moved a lot of stuff to an Alix (AMD 'Geode' based) board, and consolidated a lot of my serial devices down to 2 '4 Port USB serial' adapters on that machine. This system is running FreeBSD 8.2-RC2 i386 - the USB devices appear as a bunch of: " usbus0: 12Mbps Full Speed USB v1.0 usbus1: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 uhub0: 4 ports with 4 removable, self powered uhub1: 4 ports with 4 removable, self powered ugen1.2: at usbus1 uhub2: on usbus1 uhub2: 4 ports with 4 removable, self powered ugen1.3: at usbus1 uhub3: on usbus1 uhub3: 4 ports with 4 removable, self powered ugen1.4: at usbus1 uftdi0: on usbus1 ugen1.5: at usbus1 uhub4: on usbus1 uhub4: 4 ports with 4 removable, self powered ugen1.6: at usbus1 uhub5: on usbus1 uhub5: 4 ports with 4 removable, self powered ugen1.7: at usbus1 uftdi1: on usbus1 ugen1.8: at usbus1 uftdi2: on usbus1 ugen1.9: at usbus1 uftdi3: on usbus1 ugen1.10: at usbus1 uftdi4: on usbus1 ugen1.11: at usbus1 uhub6: on usbus1 uhub6: 4 ports with 4 removable, self powered ugen1.12: at usbus1 uftdi5: on usbus1 ugen1.13: at usbus1 uftdi6: on usbus1 ugen1.14: at usbus1 uftdi7: on usbus1 ugen1.15: at usbus1 uftdi8: on usbus1 " These end up with: " cuaU0 cuaU1.init cuaU2.lock cuaU4 cuaU5.init cuaU6.lock cuaU8 cuaU0.init cuaU1.lock cuaU3 cuaU4.init cuaU5.lock cuaU7 cuaU8.init cuaU0.lock cuaU2 cuaU3.init cuaU4.lock cuaU6 cuaU7.init cuaU8.lock cuaU1 cuaU2.init cuaU3.lock cuaU5 cuaU6.init cuaU7.lock " In /dev. The FT232R is a single device I have that I suspect is a 'serial device' with a FT232R wired internally to make it a 'USB' device. This all works great, but then - at some random point (could be a few hours, could be a few days) - all those serial ports 'stop'. The FT232R appears to be unaffected. Nothing is logged in syslog (apart from a bunch of 'irate' programs claiming they can't get data from the ports, and that things are timing out) - nothing is logged on the console either. They simply 'stop'. Even a simple "tip modem" (which is mapped to /dev/cuaU8) - and worked at boot time, now fails. You get a "connected" header, but no data (either way). 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. The FTDI ports themselves are two of these things: (Despite the 'Max Value' I've used one of these on the previous FreeBSD 7.2 host for over a year, without issue). Any pointers for what I can do next time this happens to try and trouble shoot it? Obviously with nothing logged, no errors (just a lot of programs blocking on serial I/O) - I'm not too sure where to start... Thanks, -Karl