Mouse becomes unresponsive or frozen after certain applications launch

The issue isn't presenting on every boot or every time some applications open, but it is occurring often enough for me to have looked into this. I haven't found anything that I can point to directly for the cause of this issue, so here I am.

inxi:

System:
Kernel: 6.4.3-AMD arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-amd
root=UUID=e4128302-4bdb-4bfe-aebf-5a4a30c28832 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_x11 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: X670 AORUS ELITE AX v: -CF
serial: N/A
Mobo: Gigabyte model: X670 AORUS ELITE AX v: x.x serial: N/A UEFI: American
Megatrends LLC. v: F8 date: 05/17/2023
Battery:
ID-1: hidpp_battery_3 charge: 80% condition: N/A volts: 4.0 min: N/A
model: Logitech G703 LIGHTSPEED Wireless Gaming Mouse w/ HERO type: N/A
serial: <filter> status: discharging
ID-2: hidpp_battery_4 charge: 80% condition: N/A volts: 4.0 min: N/A
model: Logitech G703 LIGHTSPEED Wireless Gaming Mouse w/ HERO type: N/A
serial: <filter> status: discharging
CPU:
Info: model: AMD Ryzen 9 7950X socket: AM5 bits: 64 type: MT MCP arch: Zen 4
gen: 5 level: v4 note: check built: 2022+ process: TSMC n5 (5nm)
family: 0x19 (25) model-id: 0x61 (97) stepping: 2 microcode: 0xA601203
Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache:
L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 16 MiB desc: 16x1024 KiB
L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 4500 min/max: 3000/5880 boost: enabled
base/boost: 4500/5850 scaling: driver: acpi-cpufreq governor: performance
volts: 1.3 V ext-clock: 100 MHz cores: 1: 4500 2: 4500 3: 4500 4: 4500
5: 4500 6: 4500 7: 4500 8: 4500 9: 4500 10: 4500 11: 4500 12: 4500
13: 4500 14: 4500 15: 4500 16: 4500 17: 4500 18: 4500 19: 4500 20: 4500
21: 4500 22: 4500 23: 4500 24: 4500 25: 4500 26: 4500 27: 4500 28: 4500
29: 4500 30: 4500 31: 4500 32: 4500 bogomips: 287565
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX] vendor: ASRock
driver: amdgpu v: kernel arch: RDNA-3 code: Navi-3x process: TSMC n5 (5nm)
built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-2
empty: DP-1,DP-3,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:744c
class-ID: 0300
Device-2: AMD Raphael vendor: Gigabyte driver: amdgpu v: kernel
arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: none empty: DP-4, DP-5,
DP-6, HDMI-A-2 bus-ID: 18:00.0 chip-ID: 1002:164e class-ID: 0300
temp: 40.0 C
Display: server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00")
s-diag: 777mm (30.58")
Monitor-1: DP-2 mapped: DisplayPort-1 model: Samsung LC27G7xT
serial: <filter> built: 2022 res: 2560x1440 hz: 240 dpi: 109 gamma: 1.2
size: 597x336mm (23.5x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 720x400
API: OpenGL v: 4.6 Mesa 23.1.3 renderer: AMD Radeon RX 7900 XTX (gfx1100
LLVM 15.0.7 DRM 3.52 6.4.3-AMD) direct-render: Yes
Audio:
Device-1: AMD driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab30 class-ID: 0403
Device-2: YUAN High-Tech Development vendor: Corsair Memory driver: N/A
pcie: gen: 2 speed: 5 GT/s lanes: 4 bus-ID: 0e:00.0 chip-ID: 12ab:0710
class-ID: 0480
Device-3: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel
v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 18:00.1
chip-ID: 1002:1640 class-ID: 0403
Device-4: AMD Family 17h/19h HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 18:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-5: Elgato Systems GmbH Wave XLR driver: snd-usb-audio type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 9-1.3:4
chip-ID: 0fd9:007d class-ID: fe01 serial: <filter>
API: ALSA v: k6.4.3-AMD status: kernel-api with: aoss type: oss-emulator
tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 0.3.73 status: n/a (root, process) with:
1: wireplumber status: active 2: pw-jack type: plugin
tools: pw-cat,pw-cli,wpctl
Server-2: PulseAudio v: 16.1 status: active (root, process) with:
1: pulseaudio-alsa type: plugin 2: pulseaudio-jack type: module
tools: pacat,pactl
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 10:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp16s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
driver: N/A modules: mt7921e pcie: gen: 2 speed: 5 GT/s lanes: 1
bus-ID: 11:00.0 chip-ID: 14c3:0616 class-ID: 0280
Bluetooth:
Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-7:3 chip-ID: 0e8d:0616
class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: N/A
Drives:
Local Storage: total: 2.73 TiB used: 658.17 GiB (23.6%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 40.9 C
scheme: GPT
SMART: yes health: PASSED on: 63d 18h cycles: 312
read-units: 33,883,327 [17.3 TB] written-units: 35,514,284 [18.1 TB]
ID-2: /dev/nvme1n1 maj-min: 259:5 vendor: PNY model: CS2140 1TB SSD
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: CS214901 temp: 38.9 C
scheme: GPT
SMART: yes health: PASSED on: 29d 6h cycles: 137
read-units: 4,042,597 [2.06 TB] written-units: 4,582,065 [2.34 TB]
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 658.17 GiB (70.7%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
maj-min: 259:7
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/nvme1n1p1
maj-min: 259:6
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 658.17 GiB (70.7%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
maj-min: 259:7
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 658.17 GiB (70.7%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
maj-min: 259:7
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 658.17 GiB (70.7%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
maj-min: 259:7
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 30.51 GiB used: 2.2 MiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 68.4 C mobo: N/A
Fan Speeds (RPM): N/A
GPU: device: amdgpu temp: 40.0 C device: amdgpu temp: 55.0 C mem: 58.0 C
fan: 301 watts: 71.00
Info:
Processes: 552 Uptime: 5m wakeups: 10 Memory: total: 32 GiB note: est.
available: 30.51 GiB used: 5.89 GiB (19.3%) Init: systemd v: 253
default: graphical tool: systemctl Compilers: gcc: 13.1.1 clang: 15.0.7
Packages: pm: pacman pkgs: 1975 libs: 575
tools: gnome-software,octopi,pamac,paru Shell: fish (sudo) v: 3.6.1
default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.28
Garuda (2.6.16-1):
System install date:     2023-06-27
Last full system update: 2023-07-12
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Yes
Failed units:

Despite what this reports, I'd like to clarify that I'm not dual booting Windows on a single drive, I've made a dedicated install of Garuda to the PNY drive listed above.

This problem is occurring for me while using both the linux-zen kernel as well as the one I'm currently using, linux-amd.
When booting, I have two applications set to open at startup: Discord and Steam (Runtime). I observed that after Steam had launched and reached the default page, in my case the store, the mouse cursor stopped responding completely. The OS doesn't freeze, my keyboard remains completely responsive and the Steam store page continues as normal, it's just the mouse that stops functioning. I have a Logitech G703 wireless mouse connected by the 2.4 GHz "Lightspeed" USB dongle, but have attempted using a different mouse both before booting and plugging it in after this issue occurs, but to no avail.

Stopping the Steam application from starting avoids the issue, but typically when its eventually started the same behavior would occur. I've uninstalled the Steam application with Pacman alongside the proton-ge-custom and Protontricks apps that had a dependency for the application, and for a time it seemed that after re-installing this fixed whatever was occurring, only for the issue to return the next day.

Changing the kernel from linux-zen to linux-amd failed to resolve the issue. Though it may be a separate or unrelated issue, I want to mention another behavior I've been seeing where, periodically and regardless of activity whether idle or not, the system will slow to a crawl with the mouse cursor moving pixel by pixel in the path my mouse was last moving. Pressing the start button on my keyboard queues the input until it picks back up to full speed. This goes on anywhere from 5 seconds to upwards of 30 seconds at a time. I haven't once been able to have the System Monitor's history open to see what may be occurring but I feel like it's related to app activity in the background, probably steam, that's taking up all of a resource to do something. No downloads have occurred (at least that it showed) on Steam during those times.
I've tried using the Steam Client beta channel, but this didn't help. I've moved back to the stable branch since.

I bring up that last issue because there are times where I'll boot up and expect the mouse freeze to occur, only to have the cursor stop responding for a brief second on Steam's startup, and then continue on without issue. Even now as I type this, opening, closing, minimizing, and maximizing any application is causing the same system hangs to occur.

In addition, another strange behavior occurs where something causes the following issue to just start happening until rebooting: Anything that causes the mouse cursor to change, like hovering over an address bar or resizing a window, causes the system to hang for a split second. Even stranger, this also occurs inside of a Windows 10 VirtualBox VM. Hovering over the address bar in Microsoft Edge produces the same behavior. One notable exception to that is the overlays of video players like Youtube and PeacockTV. Causing those to appear would result in the same brief system hang. I know these are weird issues and are probably indicative of something far more complex as far is issues go, I wanted all relevant info to be known, even if they may not help resolve anything.

I haven't done anything I'd consider different from the standard user for the setup and configuration of my Garuda install, with almost everything done through Garuda apps and Pacman.

Unfortunately, the mouse freezing isn't reliably reproduced on my end but it should occur often enough for the sake of troubleshooting the issue. I'd have tested more already but I'm not as savvy with navigating the OS with only a keyboard, let alone knowing where to start looking into the issue.

Welcome :slight_smile:

From my own experience, I would recommend the MX MASTER 3S, for this PC :slight_smile: :wink:

Try

Kernel: 6.4.3-AMD-znver3 

set kernel parameter to

amd_pstate=active

Interfering transmitters excluded?

Also check journal with jctl, start software via terminal, ...

But we do not offer support for hardware or steam.

2 Likes

Hey, thanks for the kernel parameter! I am definitely not trying to have anybody troubleshoot software that is out of their control, no worries about any issues concerning specifically the hardware or steam.

I tried using the znver3 kernel with that parameter added, but immediately found that the system was freezing after any window change. Even scrolling in the konsole caused the system to hang while it updated what was being displayed.

So I went back to linux-amd with that amd_pstate param, and while I didn't have the terrible freezing like on the znver3 kernel, I did have the mouse freeze occur once again. While the mouse was non-responsive, I restarted the machine through the start menu with my keyboard and to my surprise the reboot got hung! A repeating error marking the time passed with the message:
delayedwork_callback: delayedwork queued before hidpp interface was enumerated
So whatever this is not only stopped the mouse from working but also upset the reboot process while it was occurring.

SO, I google that alongside the keywords logitech and kernel and found a helpful page where users in May were seeing their Logitech USB Receivers become unresponsive, and someone asked them to run dmesg -w while the issue was occurring, unplug their USB, and plug it back, posting the results.

I got it to happen again, ran sudo konsole, and performed the dmesg command while it was non-responsive and....


[   60.638871] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.644866] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.648866] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.653862] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.659875] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.666832] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.672871] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.680863] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.688862] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.696863] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.701867] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.707832] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.712868] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.717869] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.722867] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.727866] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.733871] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.739865] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.744832] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.751867] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.757877] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.763867] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.764865] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.770865] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.776867] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.782862] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.789871] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.797861] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.802871] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.805866] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.814832] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.830867] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.844862] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.855866] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.863834] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.871835] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.877862] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.883862] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.889867] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.894868] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.900831] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.909870] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.911865] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.916871] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   60.931868] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   61.004866] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   61.029869] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   61.047867] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   61.066872] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   62.371866] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   62.465864] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   65.530856] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   65.535851] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   65.539850] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   65.542850] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   65.547851] delayedwork_callback: delayedwork queued before hidpp interface was enumerated
[   65.713174] usb 9-1.4.1: USB disconnect, device number 6
[  119.892843] usb 1-2: new full-speed USB device number 3 using xhci_hcd
[  120.302891] logitech-djreceiver 0003:046D:C539.000D: hidraw4: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:13:00.0-2/input0
[  120.367855] logitech-djreceiver 0003:046D:C539.000E: hiddev3,hidraw7: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:13:00.0-2/input1
[  120.432898] logitech-djreceiver 0003:046D:C539.000F: hiddev4,hidraw8: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:13:00.0-2/input2
[  120.491729] logitech-djreceiver 0003:046D:C539.000F: device of type eQUAD Lightspeed 1 (0x0c) connected on slot 1
[  120.500796] input: Logitech G703 LS as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:08.0/0000:0c:00.0/0000:0d:0c.0/0000:13:00.0/usb1/1-2/1-2:1.2/0003:046D:C539.000F/0003:046D:4086.0010/input/input32
[  120.500912] logitech-hidpp-device 0003:046D:4086.0010: input,hidraw9: USB HID v1.11 Keyboard [Logitech G703 LS] on usb-0000:13:00.0-2/input2:1
[  121.856769] logitech-hidpp-device 0003:046D:4086.0010: HID++ 4.2 device connected.
[  131.153209] usb 1-2: USB disconnect, device number 3
[  181.662690] usb 5-1: new full-speed USB device number 2 using xhci_hcd
[  181.842748] logitech-djreceiver 0003:046D:C539.0011: hidraw4: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:18:00.3-1/input0
[  181.907977] logitech-djreceiver 0003:046D:C539.0012: hiddev3,hidraw7: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:18:00.3-1/input1
[  181.966790] logitech-djreceiver 0003:046D:C539.0013: hiddev4,hidraw8: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:18:00.3-1/input2
[  182.027640] logitech-djreceiver 0003:046D:C539.0013: device of type eQUAD Lightspeed 1 (0x0c) connected on slot 1
[  182.036723] input: Logitech G703 LS as /devices/pci0000:00/0000:00:08.1/0000:18:00.3/usb5/5-1/5-1:1.2/0003:046D:C539.0013/0003:046D:4086.0014/input/input33
[  182.036869] logitech-hidpp-device 0003:046D:4086.0014: input,hidraw9: USB HID v1.11 Keyboard [Logitech G703 LS] on usb-0000:18:00.3-1/input2:1
[  185.094636] logitech-hidpp-device 0003:046D:4086.0014: HID++ 4.2 device connected.

So an important detail to this issue that I know now is exactly how this mouse is connected to the PC. The Logitech USB Dongle is plugged into the USB Hub built into my monitor, which is a Samsung Odyssey G6. The Hub is then connected to my PC with a standard USB3.0 Type-B cable.

In the log above, the first USB disconnect seen at [ 65.713174] was when I unplugged the dongle from the monitor's USB hub, and plugging it back in yielded no response whatsoever; no message even written. So I then plugged it into the front USB port on my PC's case, then unplugged from there and plugged directly into a 3.2 port on the motherboard. Each time a response was shown for the device.

I am still in the same session as when it froze to give me the results above and the mouse is working fine. I'll be rebooting frequently to test if the issue reoccurs, as well as keeping you posted if I experience any further strange freezing or performance issues.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.