From owner-freebsd-arm@freebsd.org Sat Jun 18 02:55:26 2016 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 ABCB1A781AC for ; Sat, 18 Jun 2016 02:55:26 +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 776C729FD for ; Sat, 18 Jun 2016 02:55:26 +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 u5I2tIME039198 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 17 Jun 2016 19:55:19 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id u5I2tIqr039197; Fri, 17 Jun 2016 19:55:18 -0700 (PDT) (envelope-from fbsd) Date: Fri, 17 Jun 2016 19:55:18 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: pl2303 lockups on rpi2 Message-ID: <20160618025517.GA38492@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Jun 2016 02:55:26 -0000 I'm seeing lockups of two (out of four seemingly identical) P2303TA USB-serial adapters on rpi2 at r 301978. A sample console message is login: FreeBSD/arm (ns1.zefox.net) (ttyu0) login: uplcom0: at uhub1, port 4, addr 5 (disconnected) usbd_req_re_enumerate: addr=5, set address failed! (USB_ERR_IOERROR, ignored) usbd_setup_device_desc: getting device descriptor at addr 5 failed, USB_ERR_IOERROR usbd_req_re_enumerate: addr=5, set address failed! (USB_ERR_IOERROR, ignored) usbd_setup_device_desc: getting device descriptor at addr 5 failed, USB_ERR_IOERROR The device is stuck hard, even through unplug and replug. However, if it's plugged into a Mac running Prolific's drivers it's recognized and will then work for a while, sometimes days, on FreeBSD. The problem seems to move with the adapter from one RPI2 to the next, which suggests a bad adapter, but I'm wondering if it might also be a driver operating on the edge. I can find no evidence of difference between the four adapters: The chip packages look the same, all the numbers match and the soldering looks good. I've been hesitant to take a refund up to now, but unless somebody thinks there's a driver issue on the FreeBSD side perhaps I should change my tune.... Thanks for reading and any thoughts, bob prohaska