From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216766] New: USB enumeration lockup
Date: Fri, 02 Dec 2022 18:54:08 +0000 [thread overview]
Message-ID: <bug-216766-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216766
Bug ID: 216766
Summary: USB enumeration lockup
Product: Drivers
Version: 2.5
Kernel Version: 5.19.16 and 6.0.10
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: jan.burgmeier@gmx.de
Regression: No
Hi,
Environment:
> Lenovo ThinkPad T14s Gen 1, model 20UJS00K00
> Fedora 37
after resuming from suspend the gnome-shell/gdm hangs because of fprintd and I
was able to track this down to usb device enumeration hanging on reading the
"descriptors" sysfs file. Calls to lsusb also hang on the same file.
The error can be reproduced with all recend kernels, tested with various Fedora
Kernels, from:
> Linux jbu-laptop 5.19.16-301.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Oct 21
> 15:55:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
to:
> Linux jbu-laptop 6.0.10-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Nov 26
> 16:55:13 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Here is the backtrace from the hanging usb read:
> (gdb) bt
> #0 0x00007ffff7e77fac in read () from /lib64/libc.so.6
> #1 0x00007ffff7f90885 in read (__nbytes=256, __buf=<optimized out>, __fd=8)
> at /usr/include/bits/unistd.h:38
> #2 initialize_device (dev=dev@entry=0x5555555a87c0, busnum=busnum@entry=4
> '\004', devaddr=devaddr@entry=1 '\001',
> sysfs_dir=sysfs_dir@entry=0x5555555a87a0 "usb4",
> wrapped_fd=wrapped_fd@entry=-1) at os/linux_usbfs.c:967
> #3 0x00007ffff7f92989 in linux_enumerate_device (ctx=0x55555559f610,
> busnum=<optimized out>, devaddr=<optimized out>, sysfs_dir=0x5555555a87a0
> "usb4") at os/linux_usbfs.c:1117
> #4 0x00007ffff7f93115 in linux_udev_scan_devices (ctx=0x55555559f610) at
> os/linux_udev.c:299
> #5 linux_scan_devices (ctx=0x55555559f610) at os/linux_usbfs.c:458
> #6 op_init (ctx=ctx@entry=0x55555559f610) at os/linux_usbfs.c:410
> #7 0x00007ffff7f93e79 in libusb_init (ctx=ctx@entry=0x7fffffffe138) at
> /usr/src/debug/libusb1-1.0.25-9.fc37.x86_64/libusb/core.c:2353
> #8 0x0000555555565e23 in main (argc=<optimized out>, argv=0x7fffffffe398) at
> /usr/src/debug/usbutils-014-3.fc37.x86_64/lsusb.c:3895
USB4 seems to be the integrated card reader:
> [root@jbu-laptop ~]# lsusb
> Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 006 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth
> Bus 006 Device 002: ID 06cb:00bd Synaptics, Inc. Prometheus MIS Touch
> Fingerprint Reader
> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 004 Device 002: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
> Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 002 Device 002: ID 13d3:5405 IMC Networks Integrated Camera
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The repoduction is not that easy and I'm not able to reliably reproduce the
issue mostly it works if I do the following:
1. Connect to docking station with Monitors, Headset and webcam attached
2. Suspend while connected to the docking station
3. Disconnect from the docking station
4. Resume while disconnected from the docking station
Please let me know if you need any further logs I can gather them if the next
hang occures.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-12-02 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 18:54 bugzilla-daemon [this message]
2022-12-02 20:27 ` [Bug 216766] USB enumeration lockup bugzilla-daemon
2022-12-02 21:09 ` bugzilla-daemon
2022-12-03 2:51 ` bugzilla-daemon
2022-12-03 14:32 ` bugzilla-daemon
2022-12-05 15:58 ` bugzilla-daemon
2022-12-05 16:06 ` bugzilla-daemon
2022-12-05 18:32 ` bugzilla-daemon
2022-12-05 18:33 ` bugzilla-daemon
2022-12-05 18:34 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-216766-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox