Today there were some updates (see below) which I installed using “sudo dnf update --refresh”.
After I rebooted, my mouse constantly freezes for ~0.5 second in few seconds intervals. I could say the system freezes, but hard to notice. I just noticed Firefox while scrolling to freeze, but it could be the mouse not working.
Since it is very annoying, I restored to a previous state using Timeshift and the problem was solved. After I was 100% sure that it is not happening, I re-installed the updates, and unfortunately it came back, so it is definitely something from the update.
Nothing shady… Except that “Isolated Web Co” which I am not sure what it is, and reached 70% at some point, but without freezing the mouse.
When the mouse froze, the higher app was plasmashell with 7%.
3309 username 20 0 3179764 420568 111804 S 3.0 0.6 0:42.48 Isolated Web Co
2244 username 20 0 3433760 240616 164620 S 1.3 0.4 1:26.26 kwin_wayland
17603 username 20 0 1518736 124168 107144 S 1.0 0.2 0:02.29 konsole
3152 username 20 0 12.0g 643544 286152 S 0.7 1.0 4:19.93 firefox
3298 username 20 0 7475568 361444 105592 S 0.7 0.6 0:35.61 Isolated Web Co
2405 username 20 0 4909832 484804 169260 S 0.3 0.7 0:41.37 plasmashell
2511 username 20 0 623752 33728 28864 S 0.3 0.1 0:15.02 ksystemstats
2757 username 20 0 1030536 93372 78836 S 0.3 0.1 0:09.06 openrgb
4166 username 20 0 2733504 124160 83668 S 0.3 0.2 0:01.95 Isolated Web Co
4533 username 20 0 6949520 129112 91088 S 0.3 0.2 0:01.31 Isolated Web Co
Errors in dmesg are few. The one with amdgpu is already being reported in github (by me and others)
[ 23.020042] amdgpu 0000:15:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
[ 23.905519] usb 3-12.1: reset high-speed USB device number 6 using xhci_hcd
[ 24.185301] warning: `QSampleCache::L' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[ 25.098332] Bluetooth: RFCOMM TTY layer initialized
[ 25.098347] Bluetooth: RFCOMM socket layer initialized
[ 25.098355] Bluetooth: RFCOMM ver 1.11
[ 37.178387] systemd-journald[922]: /var/log/journal/086fe2e6159d4a2fae816f891cf3cf19/user-1000.journal: Journal file uses a different sequence number ID, rotating.
[ 41.216316] nouveau 0000:01:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[ 41.216843] nouveau 0000:01:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[ 41.217382] nouveau 0000:01:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[ 41.217895] nouveau 0000:01:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[ 41.220020] nouveau 0000:01:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[ 41.221436] nouveau 0000:01:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[ 41.222358] nouveau 0000:01:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[ 41.223484] nouveau 0000:01:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[ 41.225177] nouveau 0000:01:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[ 41.225755] nouveau 0000:01:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[ 41.226371] nouveau 0000:01:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[ 41.226939] nouveau 0000:01:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
[ 426.199163] EXT4-fs (nvme1n1p1): mounted filesystem 46bf8012-c62f-4e73-af3d-e4e8947e1589 r/w with ordered data mode. Quota mode: none.
[ 426.283884] EXT4-fs (nvme1n1p1): unmounting filesystem 46bf8012-c62f-4e73-af3d-e4e8947e1589.
[ 1299.487778] amdgpu 0000:15:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
[ 1303.479357] amdgpu 0000:15:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
[ 2436.080568] xhci_hcd 0000:10:00.0: xHC error in resume, USBSTS 0x401, Reinit
[ 2436.080573] usb usb1: root hub lost power or was reset
[ 2436.080574] usb usb2: root hub lost power or was reset
[ 2436.455650] usb 1-9: reset full-speed USB device number 2 using xhci_hcd
[ 2645.348981] pcieport 0000:00:02.1: AER: Correctable error message received from 0000:09:00.0
[ 2645.348997] pcieport 0000:09:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[ 2645.349000] pcieport 0000:09:00.0: device [1022:43f4] error status/mask=00002040/00006000
[ 2645.349002] pcieport 0000:09:00.0: [ 6] BadTLP
I do have USB hubs and a KVM that I use, where my mouse/keyb are connected.
Since I work with two PC’s at the same time, I cannot remove it.
However, as I said, doesn’t happen with 6.10.7-200 version.
Try comparing the output of lsusb -v when booted under each kernel.
Do you see a difference in the bHubContrCurrent values?
I’m wondering if the kernel is getting the current calculation wrong?
Your way of doing the update has always worked for me in the past.
I just tested changes to /etc/default/grub and ran grub2-mkdonfig and the changes do appear in /etc/kernel/cmdline.
I have tested the command given by Barry above and it does update that file as well as all other changes performed by manually updating /etc/default/grub and running grub2-mkconfig. After using grubby and rebooting the changes should appear in /proc/cmdline.
Using grubby is simpler for me since you do not have to enter the path for the output file.