Date: Fri, 21 Aug 2020 18:13:08 +0000 From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished" Message-ID: <bug-237666-19105-TkdHFrdKdd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-237666-19105@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 Bjoern A. Zeeb <bz@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bz@FreeBSD.org --- Comment #121 from Bjoern A. Zeeb <bz@FreeBSD.org> --- Hi, I just unplugged a USB hub (cascade) USB-C (usb3 port) -> usb2 hub -> usb2 hub -> 3 uftdis and another uftdi at the first usb2 hub. After that console endlessly started to scroll with: uhub_reattach_port: giving up port reset - device vanished uhub_reattach_port: giving up port reset - device vanished uhub_reattach_port: giving up port reset - device vanished uhub_reattach_port: giving up port reset - device vanished uhub_reattach_port: giving up port reset - device vanished uhub_reattach_port: giving up port reset - device vanished uhub_reattach_port: giving up port reset - device vanished uhub_reattach_port: giving up port reset - device vanished as well and didn't clear up. It is clear the device is gone and it is correct, why do we not clean this up? I did run usbconfig in another shell and it is locked: # usbconfig load: 0.03 cmd: usbconfig 5017 [USB config SX lock] 1.36r 0.00u 0.00s 0% 2496k mi_switch+0xc1 sleepq_catch_signals+0x3d1 sleepq_wait_sig+0x9 _sx_xlock_hard+0x451 usbd_enum_lock_sig+0xa1 usb_ref_device+0x221 usb_open+0x106 devfs_open+0x145 VOP_OPEN_APV+0x1c vn_open_vnode+0x1eb vn_open_cred+0x3b7 kern_openat+0x249 amd64_syscall+0x119 fast_syscall_common+0xf8 (coming back to this now after applying the two sysctls mentioned in this thread I see): ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) Which is not all that is there on this either... I have saved some logs but I don't know how long I can keep the device in this state (probably another hour or so). I'll save as much dmesg/log I can. In case you want me to quickly test something let me know. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237666-19105-TkdHFrdKdd>