driesm.michiels_at_gmail.com wrote: > I just want to add a "me to" here. > > With a recent upgrade of CURRENT on my laptop, these error messages started > popping up. > Possibly not really harming anything under the hood though. Looks like r365029 fixed it for me, and even ubt0 is back happily spamming console with netgraph warnings; didn't notice its absence as I'm not using bluetooth at the moment. >> -----Original Message----- >> From: owner-freebsd-current_at_freebsd.org <owner-freebsd- >> current_at_freebsd.org> On Behalf Of Yuri Pankov >> Sent: Thursday, 27 August 2020 21:18 >> To: bob prohaska <fbsd_at_www.zefox.net> >> Cc: current_at_freebsd.org >> Subject: Re: usbd_setup_device_desc: getting device descriptor at addr 6 >> failed, USB_ERR_IOERROR >> >> bob prohaska wrote: >>> On Thu, Aug 27, 2020 at 09:41:16PM +0300, Yuri Pankov wrote: >>>> Another issue that I started seeing lately, didn't try finding out >>>> when exactly in case someone knows what it's about: >>>> >>>> Root mount waiting for: usbus0 >>>> usbd_setup_device_desc: getting device descriptor at addr 6 failed, >>>> USB_ERR_IOERROR >>>> >>> [details snipped] >>> >>>> So far not seeing any ill effects from this, i.e. I can connect USB >>>> HDD to these ports, and it's successfully detected. >>> >>> If it's convenient, connecting a USB-serial adapter and rebooting >>> might be interesting. I'm having trouble with FT232 obstructing disk >>> detection in some cases and self-disconnecting in others on a Pi3B. >> >> Don't have one. It is "desktop" PC, so the only USB devices I have/need > are >> keyboard/mouse and memsticks.Received on Tue Sep 01 2020 - 19:12:52 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:25 UTC