Date: Mon, 18 Jul 2016 16:40:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 211205] USB_ERR_TIMEOUT errors after upgrade from 10.2 Message-ID: <bug-211205-6@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211205 Bug ID: 211205 Summary: USB_ERR_TIMEOUT errors after upgrade from 10.2 Product: Base System Version: 10.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: usb Assignee: freebsd-usb@FreeBSD.org Reporter: dwvcfii@gmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Created attachment 172668 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D172668&action= =3Dedit dmesg output from Intel NUC running 10.3-RELEASE Had 10.2-RELEASE running stable on an Intel NUC (i5) for the past six month= s.=20 Decided to upgrade to 10.3-RELEASE using freebsd-update. On the first boot with the new kernel I began experiencing problems with the USB subsystem -- specifically, neither my USB keyboard nor USB mouse work anymore. Instead I get several warnings in the logs (and on the console): Jul 18 12:16:47 ren kernel: usbd_setup_device_desc: getting device descript= or at addr 1 failed, USB_ERR_TIMEOUT Jul 18 12:17:19 ren last message repeated 3 times Jul 18 12:17:30 ren kernel: usbd_setup_device_desc: getting device descript= or at addr 1 failed, USB_ERR_TIMEOUT Jul 18 12:17:30 ren kernel: ugen0.2: <Unknown> at usbus0 (disconnected) Jul 18 12:17:30 ren kernel: uhub_reattach_port: could not allocate new devi= ce When I boot without keyboard and mouse the machine boots as quickly as it usually does and I see no obvious error messages. I completed the upgrade process by calling "freebsd-update install" again to install the userspace stuff. Rebooted. Did another fetch and install to m= ake sure I was up to date. I searched online for the problem and found this thread: https://lists.freebsd.org/pipermail/freebsd-current/2016-February/059767.ht= ml and tried the suggested solution (tweak to /boot/loader.conf). It had no effect, so I removed it. I have attached dmesg output of two boot cycles -- the first with the keybo= ard (and the errors), and the second without. In both cases, the XHCI and EHCI controllers appear to be recognized without error. usbconfig confirms: ugen1.1: <EHCI root HUB Intel> at usbus1, cfg=3D0 md=3DHOST spd=3DHIGH (480= Mbps) pwr=3DSAVE (0mA) ugen0.1: <XHCI root HUB 0x8086> at usbus0, cfg=3D0 md=3DHOST spd=3DSUPER (5= .0Gbps) pwr=3DSAVE (0mA) ugen1.2: <product 0x8001 vendor 0x8087> at usbus1, cfg=3D0 md=3DHOST spd=3D= HIGH (480Mbps) pwr=3DSAVE (0mA) I want to emphasize that the keyboard and mouse are the same units as prior= to the upgrade and were working with 10.2 without issue so this isn't strictly= a hardware compatibility issue. Something changed in the 10.3 USB subsystem = that breaks select (low speed in this case) USB device instantiation. Note also that I am plugging the keyboard and mouse into the rear ports of = the NUC, which I believe are USB2 only. The Superspeed ports are on the front.= I tried plugging the keyboard into the superspeed ports and I have the same problem. The devices won't instantiate. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211205-6>