Date: Tue, 26 Mar 2019 08:15:07 +0100 From: Phil Norman <philnorm@gmail.com> To: =?UTF-8?B?R29yYW4gTWVracSH?= <meka@tilda.center> Cc: freebsd-usb@freebsd.org Subject: Re: XHCI reseting controller Message-ID: <CAOa8eG64P=2VdpADbM5iQdHsWcpmBJNmDpicNP9kuuPvUN6-RA@mail.gmail.com> In-Reply-To: <20190325233046.rsgjjs7ewlrkyr55@thinker.home.meka.rs> References: <20190325233046.rsgjjs7ewlrkyr55@thinker.home.meka.rs>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi I'm afraid, as far as I can tell, you're out of luck here. I have the mini-ITX version of the same-named board, and it shows exactly the same problem. I haven't tried it on Windows, as I don't have a copy. The best workaround I've found is to, every time I want to reboot, to a shutdown, then turn the power off completely (turning off the hardware switch on the PSU for some seconds, then switching it on before booting). This makes the USB system stable on boot, although I suggest avoiding plugging/unplugging USB devices, as it seems to create problems if done enough times. After a hard, power-off reboot like this, I've found the USB system is stable for many days - I've had it running over a month without issues. But any simple reboot will make it come back again. If you ever find a better workaround for this, please let me know. Good luck, Phil On Tue, 26 Mar 2019, 00:31 Goran Meki=C4=87, <meka@tilda.center> wrote: > Hello, > > I have > https://www.asrock.com/MB/AMD/Fatal1ty%20X370%20Professional%20Gaming/ind= ex.asp > and I have the following in my log: > > xhci0: Resetting controller > usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored) > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT > usbd_req_re_enumerate: addr=3D2, set address failed! (USB_ERR_TIMEOUT, > ignored) > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT > usbd_req_re_enumerate: addr=3D2, set address failed! (USB_ERR_TIMEOUT, > ignored) > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT > usbd_req_re_enumerate: addr=3D2, set address failed! (USB_ERR_TIMEOUT, > ignored) > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT > usbd_req_re_enumerate: addr=3D2, set address failed! (USB_ERR_TIMEOUT, > ignored) > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT > ugen0.2: <Unknown > at usbus0 (disconnected) > uhub_reattach_port: could not allocate new device > usb_alloc_device: device init 2 failed (USB_ERR_TIMEOUT, ignored) > ugen0.2: <Unknown > at usbus0 (disconnected) > uhub_reattach_port: could not allocate new device > uhub2: at usbus0, port 1, addr 1 (disconnected) > uhub2: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 > uhub2: 22 ports with 22 removable, self powered > xhci0: Resetting controller > usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored) > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT > usbd_req_re_enumerate: addr=3D2, set address failed! (USB_ERR_TIMEOUT, > ignored) > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT > usbd_req_re_enumerate: addr=3D2, set address failed! (USB_ERR_TIMEOUT, > ignored) > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT > usbd_req_re_enumerate: addr=3D2, set address failed! (USB_ERR_TIMEOUT, > ignored) > > It goes on forewer. I see USB Gen2 on the board. Can that be the cause? > How do I determine the cause at all? On Windows, all USB port work, I > tested with USB audio interface. > > Currently running 13-CURRENT, tested with 12.0-RELEASE and Ubuntu, they > all have the problem except for Windows. When I run "usbconfig" it just > hangs. Any tips are welcome, even those on how to disable problematic por= ts. > > Regards, > meka >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOa8eG64P=2VdpADbM5iQdHsWcpmBJNmDpicNP9kuuPvUN6-RA>