Bugzilla – Bug 1216786
After a reboot, Tumbleweed loses two HUBs
Last modified: 2023-11-27 15:53:33 UTC
Created attachment 870559 [details] lsusb printing when the computer is started from the power on button. The latest software update causes the two HUB/USB ports to disappear after a reboot. When the computer is started from the power-on button, each USB works OK. But when the computer is restarted with the reboot command, the two USB ports no longer work (they are like dead).Software with Kernel 6.5.8-1-default (64-bit) works incorrectly in the same way. I don't know what attachments to add so I hope you ask for them. Operating System: openSUSE Tumbleweed 20231030 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: MINIPC PN52
Created attachment 870560 [details] lsusb printing when the computer is started with the reboot command.
Created attachment 870561 [details] Details lsusb printing when the computer is started with the reboot command. New try
Created attachment 870562 [details] lsusb -v command list
Hi Ritva, is this a laptop or a desktop? if its a laptop, do you notice a difference when starting the computer with power connected vs disconnected?
(In reply to Santiago Zarate from comment #4) > Hi Ritva, is this a laptop or a desktop? if its a laptop, do you notice a > difference when starting the computer with power connected vs disconnected? It is desktop. https://www.asus.com/fi/displays-desktops/mini-pcs/pn-series/asus-expertcenter-pn52/
Created attachment 870563 [details] inxi -F command list
Created attachment 870569 [details] journalctl list when computer is restarted with reboot command
Created attachment 870571 [details] dmesg command list
When you boot 6.5.3 kernel with the rest same system, it's still working? The TW kernel will be switched to 6.6 sooner or later, so it's better to test 6.6 kernel from OBS Kernel:stable repo, too.
(In reply to Takashi Iwai from comment #9) > When you boot 6.5.3 kernel with the rest same system, it's still working? > > The TW kernel will be switched to 6.6 sooner or later, so it's better to > test 6.6 kernel from OBS Kernel:stable repo, too. I didn't just update the kernel but the entire Software (openSUSE Tumbleweed 20230917 / Kernel Version: 6.5.3-1-default). I like to test the old kernel 6.5.3-1 in this software 20231031, but I don't know how to install the old kernel in the new SW.
6.5.4 kernel is still found in TW history repo, http://download.opensuse.org/history/ Download kernel-default-6.5.4.*.rpm, and install it manually via zypper install with --oldpackage option. Then boot with that kernel and test.
(In reply to Takashi Iwai from comment #11) > 6.5.4 kernel is still found in TW history repo, > http://download.opensuse.org/history/ > > Download kernel-default-6.5.4.*.rpm, and install it manually via zypper > install with --oldpackage option. Then boot with that kernel and test. Sorry, I don't find it. Too many dictories.
Go to: http://download.opensuse.org/history/20231006/tumbleweed/repo/oss/x86_64/
(In reply to Takashi Iwai from comment #13) > Go to: > http://download.opensuse.org/history/20231006/tumbleweed/repo/oss/x86_64/ Now I was able to install the old kernel. And the USB ports work again. Operating System: openSUSE Tumbleweed 20231031 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.4-1-default (64-bit) <----------- Graphics Platform: X11 Processors: 16 x AMD Ryzen 9 5900HX with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: MINIPC PN52 machine1:~ # lsusb Bus 006 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 003: ID 0489:e0e2 Foxconn / Hon Hai Wireless_Device Bus 005 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub Bus 005 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 003 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 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 046d:c542 Logitech, Inc. M185 compact wireless mouse Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub machine1:~ # machine1:~ # machine1:~ # uname -r 6.5.4-1-default machine1:~ #
OK, then check other 6.5.x kernels, too. e.g. 6.5.6: http://download.opensuse.org/history/20231020/tumbleweed/repo/oss/x86_64/ 6.5.8: http://download.opensuse.org/history/20231026/tumbleweed/repo/oss/x86_64/ Similarly, you can try the fresh 6.6 kernel, too: http://download.opensuse.org/repositories/Kernel:/stable/standard/x86_64/
(In reply to Takashi Iwai from comment #15) > OK, then check other 6.5.x kernels, too. e.g. > 6.5.6: > http://download.opensuse.org/history/20231020/tumbleweed/repo/oss/x86_64/ > 6.5.8: > http://download.opensuse.org/history/20231026/tumbleweed/repo/oss/x86_64/ > > Similarly, you can try the fresh 6.6 kernel, too: > http://download.opensuse.org/repositories/Kernel:/stable/standard/x86_64/ I have been researching this USB problem for many hours. The problem is not only in Tumbleweed, but also in Linux Mint version 21.2 at least. I've even humbled myself to install Windows 11 and there those 2 USB ports work erratically (sometimes it works sometimes it doesn't - at least in my opinion). The reason apparently turned out to be Samsung's new SSD, i.e. this: https://www.amazon.com/Electronics-Heatsink-Internal-Compatible-MZ-V8P1T0CW/dp/B09JHL33X7?th=1 An older Samsung SSD works fine. I think it is this: https://www.samsung.com/fi/memory-storage/nvme-ssd/980-1tb-nvme-pcie-gen-3-mz-v8v1t0bw/ When I swapped the old Samsung SSD back into my computer, the USB ports worked fine with the two openSUSE packages, but not anymore when I swapped the newer SSD back. So: There were no problems with the USB ports when using an older Samsung SSD. I only tested openSUSE Tumbleweed 202309?? (6.5.3-1 default) and openSUSE Tumbleweed 20231031 (6.5.9-1 default). When using a new Samsung SSD, the USB error occurred on openSUSE Tumbleweed 20231031 (6.5.9-1 default) and Linux Mint 21.2 Xfce (5.15.0-88 common). I am completely confused with this USB issue.
I tested the new kernel, i.e. kernel-default-6.6.0-5.1.ga6606bd.x86_64.rpm, but it worked the same way as previous kernels. Also it Lost 2 USB ports after reboot command.
Created attachment 870642 [details] Picture of the BIOS when the computer is restarted with the reboot command. Picture of the BIOS when the computer is restarted with the reboot command. Note The picture shows ASUS PN52 ACPI BIOS Revision 11300, but the revision is now 11800 because I updated it after taking that picture.
We need to know whether it's a regression in the kernel code or not. When you boot with the older good kernel (e.g. 6.5.4) and the new SSD, does it still work? Or does it show the problem, too?
(In reply to Takashi Iwai from comment #19) > We need to know whether it's a regression in the kernel code or not. > When you boot with the older good kernel (e.g. 6.5.4) and the new SSD, does > it still work? Or does it show the problem, too? When I boot with the older good kernel 6.5.4 and the new SSD, it shows the same problem. All openSUSE Tumbleweeds and also Linux Mints have malfunctioned when a new SSD has been used.
(In reply to Ritva Opas from comment #20) > (In reply to Takashi Iwai from comment #19) > > We need to know whether it's a regression in the kernel code or not. > > When you boot with the older good kernel (e.g. 6.5.4) and the new SSD, does > > it still work? Or does it show the problem, too? > > When I boot with the older good kernel 6.5.4 and the new SSD, it shows the > same problem. > All openSUSE Tumbleweeds and also Linux Mints have malfunctioned when a new > SSD has been used. OK, it means that it's no regression, but it's been already broken with your new SSD, at least.
(In reply to Takashi Iwai from comment #21) > (In reply to Ritva Opas from comment #20) > > (In reply to Takashi Iwai from comment #19) > > > We need to know whether it's a regression in the kernel code or not. > > > When you boot with the older good kernel (e.g. 6.5.4) and the new SSD, does > > > it still work? Or does it show the problem, too? > > > > When I boot with the older good kernel 6.5.4 and the new SSD, it shows the > > same problem. > > All openSUSE Tumbleweeds and also Linux Mints have malfunctioned when a new > > SSD has been used. > > OK, it means that it's no regression, but it's been already broken with your > new SSD, at least. It is so. But I retested Windows 11 and it didn't have this problem. I must have messed with the Logitech receivers and USB ports, when you claim that the problem is that the ports do not work reliably with Windows. It was a bit difficult to test when I had to move the USB receivers from one port to another to check if the ports work. I changed the test arrangement in such a way that I changed the Logitech USB receivers to ports that always work. That way I always had a working mouse and keyboard. Then I switch a blank external Transcend StoreJet disk to the problem port. From the Transcend StoreJet LED, I can see if there is any life on the disc. I took dmesg prints from both boot cases. Would you like to receive them as attachments?
Google Translate translated this incorrectly: "But I retested Windows 11 and it didn't have this problem. I must have messed with the Logitech receivers and USB ports, when you claim that the problem is that the ports do not work reliably with Windows." Should be: "But I retested Windows 11 and it didn't have this problem. I must have messed with the Logitech receivers and USB ports, when I claim that the problem is that the ports do not work reliably with Windows."
when I compared the dmesg files, I found the text below in the reboot file, but this is not in the poweroff/on file. [ 1.742444] r8125 Copyright (C) 2023 Realtek NIC software team <nicfae@realtek.com> This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licenses/>. This is free software, and you are welcome to redistribute it under certain conditions; see <http://www.gnu.org/licenses/>. [ 1.742489] BTRFS info (device nvme0n1p2): enabling ssd optimizations [ 1.742492] BTRFS info (device nvme0n1p2): auto enabling async discard [ 1.946905] usb 3-2: new high-speed USB device number 2 using xhci_hcd [ 1.951872] ata2: SATA link down (SStatus 0 SControl 300) [ 1.951886] ata1: SATA link down (SStatus 0 SControl 300) [ 2.170508] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: [ 2.170514] clocksource: 'hpet' wd_nsec: 604902089 wd_now: 1d070fe wd_last: 14c4895 mask: ffffffff [ 2.170516] clocksource: 'tsc' cs_nsec: 600293870 cs_now: f296617c8 cs_last: eb2a3f653 mask: ffffffffffffffff [ 2.170518] clocksource: Clocksource 'tsc' skewed -4608219 ns (-4 ms) over watchdog 'hpet' interval of 604902089 ns (604 ms) [ 2.170520] clocksource: 'tsc' is current clocksource. [ 2.170523] tsc: Marking TSC unstable due to clocksource watchdog [ 2.170529] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [ 2.170530] sched_clock: Marking unstable (2170331366, 200762)<-(2175751917, -5223018) [ 2.170638] clocksource: Checking clocksource tsc synchronization from CPU 6 to CPUs 0,7,9,11,13-14. [ 2.170713] clocksource: Switched to clocksource hpet [ 2.276860] usb 3-2: New USB device found, idVendor=174c, idProduct=2074, bcdDevice= 0.01 [ 2.276865] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=0 [ 2.276868] usb 3-2: Product: ASM107x
I have been trying to get this problem to appear but I can't get it anymore. All USB ports work as they should. I think the bug has been fixed in kernel version 6.6-? Currently, I use kernel-default 6.6.2-1.1. raija@localhost:~> lsusb Bus 006 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 003: ID 0489:e0e2 Foxconn / Hon Hai Wireless_Device Bus 005 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub Bus 005 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 003 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 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 046d:c542 Logitech, Inc. M185 compact wireless mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub raija@localhost:~>
OK, then let's assume that it's fixed in 6.6.2 (at least). Feel free to reopen if you encounter the same problem again. Thanks.