From owner-freebsd-current@freebsd.org Thu Aug 27 17:02:19 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0217D3B8CC3; Thu, 27 Aug 2020 17:02:19 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Bcptd3pm2z3gq8; Thu, 27 Aug 2020 17:02:17 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id 07RH2LS9024400 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 27 Aug 2020 10:02:22 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id 07RH2LAU024399; Thu, 27 Aug 2020 10:02:21 -0700 (PDT) (envelope-from fbsd) Date: Thu, 27 Aug 2020 10:02:21 -0700 From: bob prohaska To: Hans Petter Selasky , bob prohaska Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: Strange USB loop Message-ID: <20200827170221.GA24247@www.zefox.net> References: <20200824163736.GA9845@www.zefox.net> <42038cfd-425c-c5cd-d3de-d3cace1ecd89@selasky.org> <20200825050304.GA11333@www.zefox.net> <8be06d6f-9837-cde6-1878-a25e84656d84@selasky.org> <20200825182916.GA14015@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200825182916.GA14015@www.zefox.net> X-Rspamd-Queue-Id: 4Bcptd3pm2z3gq8 X-Spamd-Bar: +++ X-Spamd-Result: default: False [3.21 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.26)[0.258]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.15)[0.146]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.91)[0.905]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-arm,freebsd-current]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2020 17:02:19 -0000 On Tue, Aug 25, 2020 at 11:29:16AM -0700, bob prohaska wrote: > With a _different_ FT232 plugged in it also came up normally. > > Both are thought to be genuine, but they are of different age > and produce different recognition messages: > > The FT232 that causes trouble reports > ugen1.4: at usbus1 > uftdi0 on uhub1 > uftdi0: on usbus1 > > The one that seems to work is newer and reports > ugen1.4: at usbus1 > uftdi0 on uhub1 > uftdi0: on usbus1 > > On balance I think the new kernel is better-behaved. Beyond that > I'm at a loss. If you can suggest other things to try please do. > > This morning I found on the console a message: uftdi0: at uhub1, port 3, addr 4 (disconnected) uftdi0: detached but, usbconfig -a repored ugen1.4: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (90mA) and lsusb says Bus /dev/usb Device /dev/ugen1.4: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC The FT232 is plugged directly into the Pi. This the newer, supposedly functional, ft232... Unplugging and replugging put on the console ugen1.4: at usbus1 (disconnected) uftdi0: at uhub1, port 3, addr 4 (disconnected) uftdi0: detached ugen1.4: at usbus1 uftdi0 on uhub1 uftdi0: on usbus1 But it still can't connect to the serial port of the correspondent host, which is up and running. Meanwhile, the FT232 which appeared faulty is working fine overnight on RaspiOS Buster. Thanks for reading, and any suggestions.... bob prohaska