Bug 264395
| Summary: | all usb devices (external and internal) stop working (framework laptop) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Jonathan Vasquez <jon> | ||||
| Component: | usb | Assignee: | freebsd-usb (Nobody) <usb> | ||||
| Status: | Closed Not A Bug | ||||||
| Severity: | Affects Only Me | CC: | emaste, freebsd, grahamperrin, hselasky, lwhsu | ||||
| Priority: | --- | ||||||
| Version: | 13.1-STABLE | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 262152 | ||||||
| Attachments: |
|
||||||
Is there anything special printed in dmesg? --HPS Nothing additional other than the output I uploaded earlier from the dmesg. A bit of the tail: uhub2: detached usbd_setup_device_desc: getting device descriptor at addr 7 failed, USB_ERR_TIMEOUT usbd_req_re_enumerate: addr=7, set address failed! (USB_ERR_IOERROR, ignored) usbd_setup_device_desc: getting device descriptor at addr 7 failed, USB_ERR_TIMEOUT ugen1.4: <Unknown > at usbus1 (disconnected) uhub_reattach_port: could not allocate new device From https://xyinn.org/blog/freebsd/framework_laptop it sounds like this may have been a hardware issue? Hey Ed, That's correct, it was a hardware issue after all these years. I've closed a few other FreeBSD bug tickets I reported related to USB issues, but I missed this one. Thanks for reminding me. - Jonathan |
Created attachment 234376 [details] dmesg Hello, I'm currently running: FreeBSD 13.1-STABLE #3 stable/13-n250947-0b666a7c13f: Tue May 31 07:27:41 EDT 2022 root@leslie:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 and I've noticed that every once in a while, all of my USB devices (either external or internal - and by internal I mean the 4 expandable type C female slots) on my Framework Laptop stop working. The on device keyboard/touchpad continue to work, but nothing else. I need to restart the machine completely for the usb devices to start working again. I remember reading in some bug a few months ago regarding some USB enumeration issues that other people were having, but I haven't been able to find that bug report again. (Thus I can't remember if the fix is in 14-CURRENT or if it was already MFCed). I also don't believe this is a hardware issue since I remember all of this working fine when I was Linux on this machine. - Jonathan