From owner-freebsd-arm@freebsd.org Wed Oct 3 17:36:28 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F322510A8110 for ; Wed, 3 Oct 2018 17:36:27 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 CF18287D5A for ; Wed, 3 Oct 2018 17:36:24 +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 w93HZkgG088196 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 3 Oct 2018 10:35:48 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w93HZdAV088195; Wed, 3 Oct 2018 10:35:39 -0700 (PDT) (envelope-from fbsd) Date: Wed, 3 Oct 2018 10:35:37 -0700 From: bob prohaska To: Emmanuel Vadot Cc: Trevor Roydhouse , freebsd-arm@freebsd.org, Mark Millard , bob prohaska Subject: Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse Message-ID: <20181003173537.GB84788@www.zefox.net> References: <20180929185213.GA58381@www.zefox.net> <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> <20180930130930.GB58381@www.zefox.net> <20180930132928.GC58381@www.zefox.net> <20180930155055.2c35693431e8dfff4eb7d7bd@bidouilliste.com> <20180930145702.GD58381@www.zefox.net> <20181001022415.GA63212@www.zefox.net> <20181002203135.245edff2acfcbd8441d67cc3@bidouilliste.com> <20181003011930.GA84788@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181003011930.GA84788@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2018 17:36:28 -0000 On Tue, Oct 02, 2018 at 06:19:30PM -0700, bob prohaska wrote: > > As a final test, I unplugged the PL2303 USB-serial adapter which > had been in place throughout (I'd forgotten about it). On reboot > the video console emitted sporadic non-latin characters and > didn't progress past loader, far as I can tell. > > Output on the Pi3's serial console turned to complete gobbldygook, > mostly unprintable with a few latin characters sprinkled in. > I'd forgotten that the PL2303's connector shell provided local ground for the serial console signals. The intention was to eliminate ground loops in the chain of serial connections. Using the ground pin next to the Pi3's UART pins restored normal serial console operation. Repeating the boot test with _only_ Dell keyboard/hub and mouse (no other USB devices and no monitor) connected repeated the former problem with ALPHA8: Type '?' for a list of commands, 'help' for more detailed help. OK ;21;150tTimeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint Timeout poll on interrupt endpoint It looks like the system got to the loader and is stuck there. If I type "boot" just right (quickly, and perhaps at the right time) on the serial console the machine comes up to multi-user. If I unplug the mouse from the keyboard's hub and power-cycle the pattern repeats as with the mouse connected. The caps lock light on the USB keyboard does not seem active, evidently the keyboard isn't recognized at this point. With the Dell keyboard/hub connected the machine hasn't (this morning) booted past the loader. That's different from last night, likely attributable to the lack of grounding on the serial console signals. With a laptop-sized Mac-compatible keyboard (no hub) the machine comes up multi-user without error messages, recognizing the keyboard with ukbd0 on uhub1 ukbd0: on usbus0 kbd1 at ukbd0 Using a full size genuine Apple Mac keyboard with internal hub the machine boots without issue, reporting ugen0.4: at usbus0 uhub2 on uhub1 uhub2: on usbus0 uhub2: 3 ports with 2 removable, bus powered ugen0.5: at usbus0 ukbd0 on uhub2 ukbd0: on usbus0 kbd1 at ukbd0 Connecting an Amazon Essentials USB3.0 powered hub and power cycling reported no errors. Connecting the laptop-sized Mac-compatible keyboard (which worked on its own) to the hub and power cycling caused the console to report ue0: on smsc0 ue0: Ethernet address: b8:27:eb:ba:68:d5 ugen0.4: at usbus0 uhub2 on uhub1 uhub2: on usbus0 uhub2: 4 ports with 4 removable, self powered usb_alloc_device: set address 5 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) Release APs...done It looks like hubs mixed with keyboards sometimes spell trouble, sometimes not. Apologies for the length, thanks for reading. bob prohaska