https://bugzilla.kernel.org/show_bug.cgi?id=217744 Bagas Sanjaya (bagasdotme@xxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bagasdotme@xxxxxxxxx --- Comment #3 from Bagas Sanjaya (bagasdotme@xxxxxxxxx) --- (In reply to TJ from comment #0) > Created attachment 304746 [details] > kernel log v6.5-rc4 > > On resume from suspend, since at least v6.1 and including v6.5-rc4 - an > external USB Ethernet device fails to resume due to: > > usb usb2-port3: Cannot enable. Maybe the USB cable is bad? > > Linux version 6.5.0-rc4+debian+tj (root@linux-builder) (gcc (Debian > 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #67 SMP > PREEMPT_DYNAMIC Mon Jul 31 22:25:03 BST 2023 > > DMI: LENOVO 20W6001WUS/20W6001WUS, BIOS N34ET53W (1.53 ) 08/31/2022 > > The affected owner (nickname 'Chosen_') and myself worked in Matrix Linux > room to narrow down the cause by building and testing v6.5-rc4 when the > Debian distro v6.1 showed the problem. There is no difference in the > symptoms or the kernel messages between the versions. > > Attached is the kernel log, `lspci -nnk` and `lsusb -vt`. The device is: > > /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M > ID 1d6b:0003 Linux Foundation 3.0 root hub > |__ Port 3: Dev 5, If 0, Class=Hub, Driver=hub/4p, 10000M > ID 17ef:30ab Lenovo > |__ Port 1: Dev 6, If 0, Class=Vendor Specific Class, Driver=r8152, > 5000M > ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit > Ethernet Adapter > |__ Port 3: Dev 7, If 0, Class=Hub, Driver=hub/4p, 10000M > ID 17ef:30ad Lenovo > > Which seems to be connected via the host controller on > > 00:0d.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP Thunderbolt 4 > USB Controller [8086:9a13] (rev 01) > Subsystem: Lenovo Tiger Lake-LP Thunderbolt 4 USB Controller > [17aa:22c9] > Kernel driver in use: xhci_hcd Does v6.0 not have this issue? Or is it hardware issue too? -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
