From owner-freebsd-arm@freebsd.org Fri Dec 22 02:19:17 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2779EE9D731 for ; Fri, 22 Dec 2017 02:19:17 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F29A62D3E for ; Fri, 22 Dec 2017 02:19:16 +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 vBM2J9cW021758 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 21 Dec 2017 18:19:10 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id vBM2J9Lr021757; Thu, 21 Dec 2017 18:19:09 -0800 (PST) (envelope-from fbsd) Date: Thu, 21 Dec 2017 18:19:09 -0800 From: bob prohaska To: "Rodney W. Grimes" Cc: "Jukka A. Ukkonen" , freebsd-arm@freebsd.org, bob prohaska Subject: Re: Disapearing pl2303 usb serial adapter on rpi2 Message-ID: <20171222021909.GB20324@www.zefox.net> References: <20171221161120.GA20324@www.zefox.net> <201712211619.vBLGJhpM032044@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201712211619.vBLGJhpM032044@pdx.rh.CN85.dnsmgr.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Dec 2017 02:19:17 -0000 On Thu, Dec 21, 2017 at 08:19:43AM -0800, Rodney W. Grimes wrote: > > What do you mean by unpowering both ends? > If this is one of the serial adapters that has a power pin > to plug in with the Gnd/Rx/Tx pins I would highly recommend > you leave that power pin disconnected as connecting it can > lead to power supplies in parallel and "that is a bad thing". > -- > Rod Grimes rgrimes@freebsd.org I should have written "disconnecting". The red wire wasn't in use. In the past unplugging and replugging the pl2303's usb connector by itself wouldn't allow FreeBSD to recognize the adapter, it was necessary to also unplug the data pigtails. The same appears true now; the adapter wasn't recognized by FreeBSD, despite repeated disconnect/reconnect cycles of the usb connector, but removed to an RPI3 (running Raspbian) it was recognized immediately. When moved back to the RPI2 running -current, it was recognized and at the moment seems to behave normally. For now I'll just leave it alone to see how long it stays up. I've got four of these adapters, and they all seem to exhibit the same behavior, but not to the same extent, among the four RPI2's on my local network. Two FTDI usb/serial adapters were substituted for the two most troublesome pl2303 devices, and all was well until the update to r326951. Is there a way to determine where/what is getting stuck? There seem to be at least three possibilities: usb, ucom and uplcom. Other usb devices seem unaffected. Thanks for reading, and any suggestions. bob prohaska