Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#80178 - [linux] Hang reading USB product/manufacturer
Attached to Project:
Arch Linux
Opened by AK (Andreaskem) - Monday, 06 November 2023, 11:17 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 22 November 2023, 00:48 GMT
Opened by AK (Andreaskem) - Monday, 06 November 2023, 11:17 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 22 November 2023, 00:48 GMT
|
DetailsDescription:
This is a weird issue and I am not sure where to put the blame. A few weeks ago I noticed that udev processes kept holding up the machine shutdown and I had to hard power off the system. Initially, I thought it was a one-off issue and did not immediately go into troubleshooting mode. It kept occurring, though, but only when shutting down the system at night and I kept forgetting the next day, so I am not quite sure when exactly it started happening. In any case, I started having issues with audio, as well and decided to finally look at what is happening on my system. I have a Creative Technology Sound Blaster G3 USB sound device that seems to work perfectly on Windows. It used to work just fine on Linux, as well. However, currently, something odd is happening. Having plugged in the device, the kernel notices Nov 06 11:45:32 ryzen7700x kernel: usb 5-1: new high-speed USB device number 2 using xhci_hcd Nov 06 11:45:33 ryzen7700x kernel: usb 5-1: config 1 interface 2 altsetting 0 bulk endpoint 0x82 has invalid maxpacket 256 Nov 06 11:45:33 ryzen7700x kernel: usb 5-1: New USB device found, idVendor=041e, idProduct=3267, bcdDevice=10.40 Nov 06 11:45:33 ryzen7700x kernel: usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=9 Nov 06 11:45:33 ryzen7700x kernel: usb 5-1: Product: Sound Blaster G3 Nov 06 11:45:33 ryzen7700x kernel: usb 5-1: Manufacturer: Creative Technology Ltd Nov 06 11:45:33 ryzen7700x kernel: usb 5-1: SerialNumber: 15C1E5E3165B9B3D Nov 06 11:45:33 ryzen7700x kernel: input: Creative Technology Ltd Sound Blaster G3 as /devices/pci0000:00/0000:00:02.1/0000:04:00.0/0000:05:0c.0/0000:17:00.0/usb5/5-1/5-1:1.0/0003:041E:3267.0007/input/input28 Nov 06 11:45:33 ryzen7700x kernel: hid-generic 0003:041E:3267.0007: input,hidraw6: USB HID v1.10 Device [Creative Technology Ltd Sound Blaster G3] on usb-0000:17:00.0-1/input0 Nov 06 11:45:38 ryzen7700x kernel: usb 5-1: parse_audio_format_rates_v2v3(): unable to find clock source (clock -110) As far as I remember, the last line has always been there, even before I noticed any issues. So far, this seems unremarkable. However, when doing a simple cat /sys/devices/pci0000:00/0000:00:02.1/0000:04:00.0/0000:05:0c.0/0000:17:00.0/usb5/5-1/manufacturer or cat /sys/devices/pci0000:00/0000:00:02.1/0000:04:00.0/0000:05:0c.0/0000:17:00.0/usb5/5-1/product The process is just stuck and does not print the manufacturer or product. This works perfectly for other USB devices, as I use several. Initially, I determined that udev was stuck with a backtrace that pointed me to the manufacturer/product ID, so I looked at these files and realized that the issue seems to lie deeper. Having unplugged and replugged the device with different ports, there appear hung kernel tasks: Nov 06 12:05:29 ryzen7700x kernel: INFO: task kworker/14:2:909 blocked for more than 368 seconds. Nov 06 12:05:29 ryzen7700x kernel: Not tainted 6.6.0-arch1-1 #1 Nov 06 12:05:29 ryzen7700x kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 06 12:05:29 ryzen7700x kernel: task:kworker/14:2 state:D stack:0 pid:909 ppid:2 flags:0x00004000 Nov 06 12:05:29 ryzen7700x kernel: Workqueue: usb_hub_wq hub_event Nov 06 12:05:29 ryzen7700x kernel: Call Trace: Nov 06 12:05:29 ryzen7700x kernel: <TASK> Nov 06 12:05:29 ryzen7700x kernel: __schedule+0x3e8/0x1410 Nov 06 12:05:29 ryzen7700x kernel: ? finish_task_switch.isra.0+0x94/0x2f0 Nov 06 12:05:29 ryzen7700x kernel: ? srso_alias_return_thunk+0x5/0x7f Nov 06 12:05:29 ryzen7700x kernel: ? __schedule+0x3f0/0x1410 Nov 06 12:05:29 ryzen7700x kernel: schedule+0x5e/0xd0 Nov 06 12:05:29 ryzen7700x kernel: schedule_preempt_disabled+0x15/0x30 Nov 06 12:05:29 ryzen7700x kernel: __mutex_lock.constprop.0+0x39a/0x6a0 Nov 06 12:05:29 ryzen7700x kernel: ? srso_alias_return_thunk+0x5/0x7f Nov 06 12:05:29 ryzen7700x kernel: ? usb_kill_urb.part.0+0xbc/0xd0 Nov 06 12:05:29 ryzen7700x kernel: usb_audio_disconnect+0x49/0x2d0 [snd_usb_audio 486540d23a6940d7bd18746690a6ba98856341b6] Nov 06 12:05:29 ryzen7700x kernel: ? srso_alias_return_thunk+0x5/0x7f Nov 06 12:05:29 ryzen7700x kernel: usb_unbind_interface+0x90/0x270 Nov 06 12:05:29 ryzen7700x kernel: device_release_driver_internal+0x19f/0x200 Nov 06 12:05:29 ryzen7700x kernel: bus_remove_device+0xc6/0x130 Nov 06 12:05:29 ryzen7700x kernel: device_del+0x15c/0x3f0 Nov 06 12:05:29 ryzen7700x kernel: ? srso_alias_return_thunk+0x5/0x7f Nov 06 12:05:29 ryzen7700x kernel: ? kobject_put+0x8d/0x190 Nov 06 12:05:29 ryzen7700x kernel: usb_disable_device+0xcd/0x1e0 Nov 06 12:05:29 ryzen7700x kernel: usb_disconnect+0xde/0x2c0 Nov 06 12:05:29 ryzen7700x kernel: hub_event+0xa0b/0x1bf0 Nov 06 12:05:29 ryzen7700x kernel: ? __pm_runtime_suspend+0x4a/0xd0 Nov 06 12:05:29 ryzen7700x kernel: process_one_work+0x171/0x340 Nov 06 12:05:29 ryzen7700x kernel: worker_thread+0x27b/0x3a0 Nov 06 12:05:29 ryzen7700x kernel: ? __pfx_worker_thread+0x10/0x10 Nov 06 12:05:29 ryzen7700x kernel: kthread+0xe5/0x120 Nov 06 12:05:29 ryzen7700x kernel: ? __pfx_kthread+0x10/0x10 Nov 06 12:05:29 ryzen7700x kernel: ret_from_fork+0x31/0x50 Nov 06 12:05:29 ryzen7700x kernel: ? __pfx_kthread+0x10/0x10 Nov 06 12:05:29 ryzen7700x kernel: ret_from_fork_asm+0x1b/0x30 Nov 06 12:05:29 ryzen7700x kernel: </TASK> What confuses me most is that I tried using the LTS kernel and nothing changed. I even went back to a mainline kernel version from the Archive from before I experienced the issue but nothing seemed to change. I looked at the stable kernel changelogs and did not immediately notice something that could be related. At this point, I am not sure how to proceed or troubleshoot any further. Additional info: * package version(s) - Linux ryzen7700x 6.6.0-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 31 Oct 2023 13:15:05 +0000 x86_64 GNU/Linux - Motherboard: ASRock X670E PG Lightning Steps to reproduce: Plug in a Sound Blaster G3 |
This task depends upon
Comment by Toolybird (Toolybird) -
Tuesday, 07 November 2023, 06:17 GMT
It's possible the device might have developed a fault...or maybe something screwy is happening with udev, but that seems unlikely if other devices are ok. What about firmware? Dunno. Either way, it doesn't seem like an Arch packaging issue. Your best bet is likely to try contacting some kernel sound folks.. or maybe take it to the support forum to see if anyone has any ideas. Please let us know what you find out.