https://bugzilla.kernel.org/show_bug.cgi?id=220069 --- Comment #25 from Claudio Wunder (cwunder@xxxxxxxxx) --- Some extra info: - This time the computer was on idle when it happened, like I wasn't even close to the PC but noticed something odd happened, hence checked and saw it was dead - Running usbreset of the controller and `yavta` on a loop for about one hour did not occur on any USB crash; So I doubt it is something related to heavy workloads on the controller. - Afaik the ASM107x device is disabled on EFI; Regarding the different slots, I'm not sure if the devices order/attachment can change on unbind/bind (I believe so) or just on a new boot, but here's the output of lspci and lsusb from the current boot (same as the crash) ``` ❯ lspci -nn | grep USB 03:00.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 31 USB [1002:7446] 0f:00.0 USB controller [0c03]: Intel Corporation Thunderbolt 4 NHI [Maple Ridge 4C 2020] [8086:1137] 3b:00.0 USB controller [0c03]: Intel Corporation Thunderbolt 4 USB Controller [Maple Ridge 4C 2020] [8086:1138] 68:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset USB 3.2 Controller [1022:43f7] (rev 01) 6a:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset USB 3.2 Controller [1022:43f7] (rev 01) 6c:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 3.1 xHCI [1022:15b6] 6c:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 3.1 xHCI [1022:15b7] 6d:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 2.0 xHCI [1022:15b8] ❯ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 19f7:0050 RODE Microphones RODECaster Duo Bus 005 Device 003: ID 8087:0032 Intel Corp. AX210 Bluetooth Bus 005 Device 004: ID 0b05:1a53 ASUSTek Computer, Inc. USB Audio Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 004: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub Bus 007 Device 006: ID 1e71:300e NZXT NZXT Kraken Base Bus 007 Device 009: ID 046d:c54d Logitech, Inc. USB Receiver Bus 007 Device 011: ID 0b05:18f3 ASUSTek Computer, Inc. AURA LED Controller Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 008 Device 004: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 012 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 013 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 014 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub ``` Also one extra info, I have an `udev` rule to prevent USB devices to wake up my PC from sleep. I doubt it has anything to do with it, but worth sharing: ``` ❯ bat /etc/udev/rules.d/99-usb-wakeup.rules ───────┬─────────────────────────────────────────────────────────── │ File: /etc/udev/rules.d/99-usb-wakeup.rules ───────┼─────────────────────────────────────────────────────────── 1 │ ACTION=="add", SUBSYSTEM=="usb", RUN+="/bin/sh -c 'echo di │ sabled > /sys/bus/usb/devices/%k/power/wakeup'" ───────┴─────────────────────────────────────────────────────────── ``` (Note the issue was happening even before this rule existed afaik) -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
