USB/Wireless Mouse Stutters

Hi all,

I have a MX Master 3S. I’ve tried using it in both (dongled) USB mode and Bluetooth mode and observe the same behavior. My mouse will “stutter” (as if it was rendering at single digit or often negative FPS), and sometimes will slowly recover. So it’ll stop, slowly jump, then start moving again at lets say 10 fps, before resuming normally. Sometimes it’ll act like it has mouse acceleration and just not stop when I stop moving the mouse (I do have accl disabled). It’d say 70% of the time it’s fine. Sometime however, I have to power cycle the mouse to get it working normally again. I’m fairly confident this issue is related to a driver or kernel module as no other element of my system will lag, stutter, or jump when this occurs. I have two mice and my other mouse (wired G420 Hero), has never done this. I’m confident this issue is not the mouse hardware as I have never experienced this behavior on MacOS or Windows on other devices. I use MacOS daily for work, and Windows frequently enough, so I feel this is worth mentioning.

Not really sure what’s going on here. I’ve tried a plethora of things, mostly from the Arch wiki (linked below). I do see errors in Journald when using it with Bluetooth, but googling them has yet to yield a solution. I do not see those same errors when using it in “dongled” mode, so I’m not confident they’re related.

Not entirely sure what to do here. Sorry if I didn’t include something, I attempted to be thorough.

System info:

╰─○ lsb_release -sirc
ManjaroLinux 24.0.0 Wynsdey
╰─○ fastfetch
...
Kernel: 6.6.30-2-MANJARO
...
DE: KDE Plasma 6.0.4
WM: KWin (Wayland)
...
╰─○ inxi -zv8        
System:
  Kernel: 6.6.30-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.6-x86_64
    root=UUID=... rw rootflags=subvol=@
    intel_iommu=on iommu=pt
    cryptdevice=UUID=...
    root=/dev/mapper/luks-... quiet splash
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A info: frameworks v: 6.1.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: MEG Z790 ACE (MS-7D86) v: 1.0
    serial: <superuser required> uuid: <superuser required> UEFI: American
    Megatrends LLC. v: 1.30 date: 03/23/2023
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 64 GiB available: 62.63 GiB used: 6.72 GiB (10.7%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 4 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Controller0-DIMMA1 type: DDR5 detail: synchronous size: 16 GiB
    speed: 5200 MT/s volts: curr: 1.35 min: 1.35 max: 1.35 width (bits):
    data: 64 total: 64 manufacturer: G Skill Intl part-no: F5-7200J3445G16G
    serial: N/A
  Device-2: Controller0-DIMMA2 type: DDR5 detail: synchronous size: 16 GiB
    speed: 5200 MT/s volts: curr: 1.35 min: 1.35 max: 1.35 width (bits):
    data: 64 total: 64 manufacturer: G Skill Intl part-no: F5-7200J3445G16G
    serial: N/A
  Device-3: Controller1-DIMMB1 type: DDR5 detail: synchronous size: 16 GiB
    speed: 5200 MT/s volts: curr: 1.35 min: 1.35 max: 1.35 width (bits):
    data: 64 total: 64 manufacturer: G Skill Intl part-no: F5-7200J3445G16G
    serial: N/A
  Device-4: Controller1-DIMMB2 type: DDR5 detail: synchronous size: 16 GiB
    speed: 5200 MT/s volts: curr: 1.35 min: 1.35 max: 1.35 width (bits):
    data: 64 total: 64 manufacturer: G Skill Intl part-no: F5-7200J3445G16G
    serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: 13th Gen Intel Core i9-13900KF bits: 64 type: MST AMCP
    arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+
    process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183) stepping: 1
    microcode: 0x122
  Topology: cpus: 1x cores: 24 mt: 8 tpc: 2 st: 16 threads: 32 smt: enabled
    cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32 KiB, 16x64 KiB
    L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
  Speed (MHz): avg: 2228 high: 5500 min/max: 800/5500:5800:4300 scaling:
    driver: intel_pstate governor: powersave cores: 1: 5500 2: 800 3: 800 4: 800
    5: 5500 6: 800 7: 800 8: 800 9: 5500 10: 800 11: 5500 12: 800 13: 5500
    14: 800 15: 5500 16: 800 17: 4294 18: 800 19: 4291 20: 800 21: 4305
    22: 800 23: 800 24: 800 25: 800 26: 800 27: 4301 28: 800 29: 800 30: 800
    31: 4309 32: 800 bogomips: 191744
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2
    bts clflush clflushopt clwb cmov constant_tsc cpuid cpuid_fault cx16 cx8
    de ds_cpl dtes64 dtherm dts ept ept_ad erms est f16c flexpriority
    flush_l1d fma fpu fsgsbase fsrm fxsr gfni hfi ht hwp hwp_act_window
    hwp_epp hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ibt ida intel_pt
    invpcid lahf_lm lm mca mce md_clear mmx monitor movbe movdir64b movdiri
    msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pclmulqdq pdcm pdpe1gb
    pebs pge pku pln pni popcnt pse pse36 pts rdpid rdrand rdseed rdtscp
    rep_good sdbg sep serialize sha_ni smap smep split_lock_detect ss ssbd
    sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc
    tsc_adjust tsc_deadline_timer tsc_known_freq umip user_shstk vaes vme vmx
    vnmi vpclmulqdq vpid waitpkg x2apic xgetbv1 xsave xsavec xsaveopt xsaves
    xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling mitigation: Clear Register File
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB:
    conditional; RSB filling; PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M] 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-1,DP-3,HDMI-A-1
    empty: DP-2 bus-ID: 03:00.0 chip-ID: 1002:744c class-ID: 0300
  Device-2: Logitech BRIO Ultra HD Webcam driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6.4.4.4:37
    chip-ID: 046d:085e class-ID: 0102 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 23.2.6
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu d-rect: 6720x2560 display-ID: 0
  Monitor-1: DP-1 pos: primary,left res: 3840x2160 size: N/A modes: N/A
  Monitor-2: DP-3 pos: center res: 1440x2560 size: N/A modes: N/A
  Monitor-3: HDMI-A-1 pos: right res: 1440x2560 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
    drv: radeonsi inactive: gbm
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.6-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 XT (radeonsi
    navi31 LLVM 17.0.6 DRM 3.54 6.6.30-2-MANJARO) device-ID: 1002:744c
    memory: 19.53 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.3.279 layers: 7 device: 0 type: discrete-gpu name: AMD
    Radeon RX 7900 XT (RADV NAVI31) driver: mesa radv v: 24.0.6-manjaro1.1
    device-ID: 1002:744c surfaces: xcb,xlib,wayland
Audio:
  Device-1: Intel Raptor Lake High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel alternate: snd_sof_pci_intel_tgl
    bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
  Device-2: AMD Navi 31 HDMI/DP Audio 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-3: Micro Star USB Audio driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-12:13
    chip-ID: 0db0:488c class-ID: 0300
  Device-4: Schiit Audio Unison Modius E driver: snd-usb-audio type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6.4.1.1:32
    chip-ID: 30be:101a class-ID: 0102
  Device-5: Mark of the Unicorn M2 driver: cdc_acm,snd-usb-audio type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6.4.4.3:36
    chip-ID: 07fd:000b class-ID: 0a00 serial: <filter>
  Device-6: Logitech BRIO Ultra HD Webcam driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6.4.4.4:37
    chip-ID: 046d:085e class-ID: 0102 serial: <filter>
  API: ALSA v: k6.6.30-2-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Raptor Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:7a70 class-ID: 0280
  IF: wlo1 state: down mac: <filter>
  Device-2: Intel 82599 10 Gigabit Network vendor: Beijing Sinead
    driver: ixgbe v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 8 port: 5000
    bus-ID: 04:00.0 chip-ID: 8086:1557 class-ID: 0200
  IF: enp4s0 state: up speed: 10000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Device-3: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
    rev: 3.0 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-4.2.1:16
    chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
  IF: enp0s20f0u4u2u1 state: down mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  Info: services: NetworkManager, sshd, systemd-timesyncd
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:22 chip-ID: 8087:0033
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: <filter> bt-v: 5.3 lmp-v: 12
    status: discoverable: no pairing: no
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-1:2 info: Genesys Logic Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 05e3:0610
    class-ID: 0900
  Device-1: 1-1.4:4 info: Logitech G502 SE HERO Gaming Mouse type: mouse,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 300mA chip-ID: 046d:c08b class-ID: 0300
    serial: <filter>
  Hub-3: 1-6:24 info: Genesys Logic Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0610 class-ID: 0900
  Hub-4: 1-6.2:25 info: Realtek 3-Port USB 2.1 Hub ports: 3 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5412
    class-ID: 0900
  Hub-5: 1-6.2.2:27 info: Realtek RTS5411 Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5411
    class-ID: 0900
  Device-1: 1-6.2.3:29 info: Realtek BillBoard Device type: billboard
    driver: N/A interfaces: 1 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 chip-ID: 0bda:5418 class-ID: 1100 serial: <filter>
  Device-2: 1-6.3:26 info: Logitech Logi Bolt Receiver
    type: keyboard,mouse,HID driver: hid-generic,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c548 class-ID: 0300
  Hub-6: 1-6.4:28 info: Genesys Logic Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0610 class-ID: 0900
  Hub-7: 1-6.4.1:30 info: Genesys Logic Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 1-6.4.1.1:32 info: Schiit Audio Unison Modius E type: audio
    driver: snd-usb-audio interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 chip-ID: 30be:101a class-ID: 0102
  Hub-8: 1-6.4.2:31 info: Genesys Logic Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0610 class-ID: 0900
  Hub-9: 1-6.4.3:33 info: Genesys Logic Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0610 class-ID: 0900
  Hub-10: 1-6.4.4:34 info: Genesys Logic Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 1-6.4.4.1:35 info: Gtech Magnetic Wired Keyboard
    type: keyboard,mouse,HID driver: hid-generic,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 400mA
    chip-ID: 36b5:2f8f class-ID: 0300
  Device-2: 1-6.4.4.3:36 info: Mark of the Unicorn M2
    type: audio,abstract (modem),CDC-data driver: cdc_acm,snd-usb-audio
    interfaces: 7 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
    power: 500mA chip-ID: 07fd:000b class-ID: 0a00 serial: <filter>
  Device-3: 1-6.4.4.4:37 info: Logitech BRIO Ultra HD Webcam
    type: video,audio driver: snd-usb-audio,uvcvideo interfaces: 5 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 046d:085e class-ID: 0102 serial: <filter>
  Hub-11: 1-7:5 info: Genesys Logic Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 05e3:0610
    class-ID: 0900
  Device-1: 1-8:7 info: Yubicom Yubikey 4/5 OTP+U2F+CCID
    type: keyboard,HID,smart card driver: hid-generic,usbhid interfaces: 3
    rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 30mA
    chip-ID: 1050:0407 class-ID: 0b00
  Device-2: 1-11:10 info: Micro Star MYSTIC LIGHT type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 1462:7d86 class-ID: 0300
    serial: <filter>
  Device-3: 1-12:13 info: Micro Star USB Audio type: audio,HID
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 8 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 0db0:488c class-ID: 0300
  Hub-12: 1-13:20 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-14:22 info: Intel AX211 Bluetooth type: bluetooth
    driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 100mA chip-ID: 8087:0033 class-ID: e001
  Hub-13: 2-0:1 info: super-speed hub ports: 8 rev: 3.1
    speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-14: 2-1:2 info: Genesys Logic USB3.2 Hub ports: 4 rev: 3.2
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 05e3:0625
    class-ID: 0900
  Hub-15: 2-4:13 info: Genesys Logic Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 05e3:0626
    class-ID: 0900
  Hub-16: 2-4.2:14 info: Realtek 2-Port USB 3.1 Hub ports: 2 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 0bda:0412
    class-ID: 0900
  Device-1: 2-4.2.1:16 info: Realtek RTL8153 Gigabit Ethernet Adapter
    type: Network driver: r8152 interfaces: 1 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 288mA
    chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
  Hub-17: 2-4.2.2:19 info: Realtek Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 0bda:0411
    class-ID: 0900
  Hub-18: 2-4.4:15 info: Genesys Logic Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 05e3:0626
    class-ID: 0900
  Hub-19: 2-4.4.1:17 info: Genesys Logic Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 05e3:0626
    class-ID: 0900
  Hub-20: 2-4.4.2:18 info: Genesys Logic Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 05e3:0626
    class-ID: 0900
  Hub-21: 2-4.4.3:20 info: Genesys Logic Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 05e3:0626
    class-ID: 0900
  Hub-22: 2-4.4.4:21 info: Genesys Logic Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 05e3:0626
    class-ID: 0900
  Hub-23: 2-8:4 info: Genesys Logic GL3523 Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 05e3:0620
    class-ID: 0900
  Hub-24: 3-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-25: 4-0:1 info: super-speed hub ports: 1 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-26: 5-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-27: 6-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A gpu: amdgpu temp: 77.0 C
    mem: 86.0 C
  Fan Speeds (rpm): cpu: 723 fan-2: 0 fan-3: 1524 fan-4: 1442 fan-5: 0
    fan-6: 0 fan-7: 0 fan-8: 0 fan-9: 0 fan-10: 0 gpu: amdgpu fan: 523
Info:
  Processes: 623 Power: uptime: 32m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 25.04 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
    tool: systemctl
  Compilers: clang: 17.0.6 gcc: 13.2.1 Shell: Zsh v: 5.9 running-in: yakuake
    inxi: 3.3.34

Read and tried (at least, what’s notable imo):

https://bbs.archlinux.org/viewtopic.php?id=272049
https://wiki.archlinux.org/title/Bluetooth_mouse#Mouse_lag
https://wiki.archlinux.org/title/Logitech_Unifying_Receiver
https://wiki.archlinux.org/title/Logitech_MX_Master

I’m observing exactly the same, since a few days as well I also have Manjaro with Plasma, since a year or so on this machine.

I can add that I see this with 3 different mice, connected to the receiver:

  • MX Master 3S (connected to a latest Bolt receiver)
  • MX Anywhere 3S (connected as the one above)
  • MX Vertical (connected to an older receiver)

Now, I’ve tried this also with Bluetooth, and I think I see the same. At seamingly random the cursor start to stutter for a few seconds, as if it lags behind and then it recovers.

I believe it is not related either to the mice, nor to some interference of sort, because I have dual-booth on this machine and I don’t observe this when running Windows 10.

❯ lsb_release -sirc
ManjaroLinux 24.0.0 Wynsdey
❯ fastfetch
                  -`                     bill@yoda
                 .o+`                    ---------
                `ooo/                    OS: Manjaro Linux Wynsdey 24.0.0 x86_64
               `+oooo:                   Kernel: 6.6.30-2-MANJARO
              `+oooooo:                  Uptime: 51 mins
              -+oooooo+:                 Packages: 1883 (pacman)[stable], 19 (flatpak)
            `/:-:++oooo+:                Shell: zsh 5.9
           `/++++/+++++++:               Display (DELL U3423WE): 3440x1440 @ 60Hz
          `/++++++++++++++:              DE: KDE Plasma 6.0.4
         `/+++ooooooooooooo/`            WM: KWin (X11)
        ./ooosssso++osssssso+`           WM Theme: Breeze
       .oossssso-````/ossssss+`          Theme: Breeze (BreathLight) [QT], Breeze [GTK2/3]
      -osssssso.      :ssssssso.         Icons: breeze [QT], breeze [GTK2/3/4]
     :osssssss/        osssso+++.        Font: Noto Sans (10pt) [QT], Noto Sans (10pt) [GTK2/3/4]
    /ossssssss/        +ssssooo/-        Cursor: breeze (24px)
  `/ossssso+/:-        -:/+osssso+-      Terminal: konsole 24.2.2
 `+sso+:-`                 `.-/+oso:     Terminal Font: MesloLGS Nerd Font (10pt)
`++:.                           `-/+/    CPU: AMD Ryzen 9 7950X3D (32) @ 5.76 GHz
.`                                 `/    GPU 1: AMD Radeon RX 6700 XT [Discrete]
                                         GPU 2: AMD Raphael @ 0.60 GHz [Integrated]
                                         Memory: 5.33 GiB / 61.95 GiB (9%)
                                         Swap: Disabled
                                         Disk (/): 54.10 GiB / 119.21 GiB (45%) - btrfs
                                         Disk (/data/BIG): 1.54 TiB / 2.69 TiB (57%) - ext4
                                         Disk (/data/FLUFFY): 199.11 GiB / 232.14 GiB (86%) - fuseblk
                                         Disk (/data/SPEEDY): 141.30 GiB / 228.89 GiB (62%) - ext4
                                         Disk (/home): 212.16 GiB / 476.83 GiB (44%) - btrfs
                                         Local IP (eno1): 192.168.1.12/24 *
                                         Locale: en_GB.UTF-8

Same Manjaro, kernel and Plasma version as the initial post from @akat , but I have X11 instead of Wayland.

As well, I’ve read and tried, where applicable, what linked just above. But these are mostly for Bluetooth mice, while I connect with the receivers.

I’m of course available to collect any info from my system if needed to help debugging, but I myself wouldn’t really know where to begin.

Thanks for any help with this :wink:

I’m not sure if this is the case for @akat as well, but I believe that on my desktop this has sort of solved by itself.
But I stil see this on my laptop, which has somewhat lower graphical HW specs. I wonder if this is related.

❯ lsb_release -sirc
ManjaroLinux 24.0.2 Wynsdey
❯ fastfetch
██████████████████  ████████    bill@apollo
██████████████████  ████████    -----------
██████████████████  ████████    OS: Manjaro Linux Wynsdey 24.0.2 x86_64
██████████████████  ████████    Host: VivoBook_ASUSLaptop TP420IA_TM420IA (1.0)
████████            ████████    Kernel: Linux 6.6.32-1-MANJARO
████████  ████████  ████████    Uptime: 9 mins
████████  ████████  ████████    Packages: 1997 (pacman)[stable], 20 (flatpak), 2 (snap)
████████  ████████  ████████    Shell: zsh 5.9
████████  ████████  ████████    Display (CMN14D4): 1920x1080 @ 60Hz
████████  ████████  ████████    DE: KDE Plasma 6.0.5
████████  ████████  ████████    WM: KWin (X11)
████████  ████████  ████████    WM Theme: Breeze
████████  ████████  ████████    Theme: Breeze (BreathDark) [QT], Breath [GTK2/3]
████████  ████████  ████████    Icons: breeze [QT], breeze [GTK2/3/4]
                                Font: Noto Sans (10pt) [QT], Noto Sans (10pt) [GTK2/3/4]
                                Cursor: breeze (24px)
                                Terminal: konsole 24.5.0
                                Terminal Font: MesloLGS NF (10pt)
                                CPU: AMD Ryzen 7 4700U (8) @ 2.00 GHz
                                GPU: AMD Radeon RX Vega 6 (Ryzen 4000/5000 Mobile Series) @ 0.40 GHz [Integrated]
                                Memory: 4.38 GiB / 15.04 GiB (29%)
                                Swap: 18.25 MiB / 16.63 GiB (0%)
                                Disk (/): 119.96 GiB / 451.72 GiB (27%) - ext4
                                Local IP (wlp1s0): 192.168.220.130/24 *
                                Battery: 85% [Discharging]
                                Locale: en_GB.UTF-8

I have the same mouse and the same behavior when connecting it near another usb wifi, the solution was a usb cable extender, to move the two devices away.

I have them 50cm. apart.

2 Likes

I have a Radeon 7900XT, and run 4k@240hz, I don’t think in my case at least it’s hardware capability related.

I will have to check later but I’m fairly certain I’m on 24.0.2 as well.

I’m glad it’s not giving you any more issues on your desktop :slight_smile:

I do not have a WiFi dongle, and the nearest device to the mouse dongle is sometimes at its nearest 2ft away, and is the only wireless device close to it. Everything else is wired.

I can’t say it isn’t at least in part RF/EMI related to the aforementioned wiring, although I have no-way to accurately measure that I don’t think. If it is, it makes me wonder if @billznn’s problem/resolution was a fluke.

I have a feeling this might be an XY problem. When I have some time In should probably work to confirm what it is and what is not caused by in greater detail.

Ultimately, I have just started using a wired mouse for my manjaro box, and I use my MX for everything else. Whatever the cause of this issue is beyond my ability to diagnose, I feel. I’ve spent close to 70 hours total trying, testing, and rolling back just about every potential solution I’ve come across to no avail.

Well, if you read just a bit above in my first reply, the issue was not there when booting to Windows, on the exact same HW config (didn’t move anything).
That’s why I singled out the issue was maybe OS related.

Also, in the laptop I have nothing connected to the BT expect the mouse, and no USB dongle.

Ah yeah, I didn’t mean the issue is related to “insufficient” performance, but maybe something related to drivers/GPU or something (on both the desktop and the laptop I have a Ryzen CPU with Radeon GPU… maybe that’s the common cause?).

Yes, I am on 24.0.2.

╭─akat at nasa in ~ 24-06-19 - 16:39:39
╰─○ fastfetch
██████████████████  ████████    akat@nasa
██████████████████  ████████    ---------
██████████████████  ████████    OS: Manjaro Linux Wynsdey 24.0.2 x86_64
██████████████████  ████████    Host: MS-7D86 (1.0)
████████            ████████    Kernel: Linux 6.6.32-1-MANJARO
████████  ████████  ████████    Uptime: 3 days, 2 hours, 21 mins
████████  ████████  ████████    Packages: 2284 (pacman)[stable], 46 (nix-default), 8 (flatpak), 32 (brew)
████████  ████████  ████████    Shell: zsh 5.9
████████  ████████  ████████    Display (Odyssey G8): 3840x2160 @ 240Hz
████████  ████████  ████████    Display (LEN P24h-20): 1440x2560 @ 75Hz [External]
████████  ████████  ████████    Display (LEN P24h-20): 1440x2560 @ 75Hz
████████  ████████  ████████    DE: KDE Plasma 6.0.5
████████  ████████  ████████    WM: KWin (Wayland)
████████  ████████  ████████    WM Theme: Breeze
                                Theme: Breeze (BreathDark) [QT], Breeze-Dark [GTK2], Breeze [GTK3]
                                Icons: breeze-dark [QT], breeze-dark [GTK2/3/4]
                                Font: Noto Sans (10pt) [QT], Noto Sans (10pt) [GTK2/3/4]
                                Cursor: oreo_black (32px)
                                Terminal: kitty 0.35.1
                                Terminal Font: NotoSansMono-Regular (11pt)
                                CPU: 13th Gen Intel(R) Core(TM) i9-13900KF (32) @ 5.80 GHz
                                GPU: AMD Radeon RX 7900 XT @ 0.02 GHz [Discrete]
                                Memory: 11.89 GiB / 62.63 GiB (19%)
                                Swap: Disabled
                                Disk (/): 436.39 GiB / 931.21 GiB (47%) - btrfs
                                Disk (/data): 815.76 GiB / 1.82 TiB (44%) - btrfs
                                Disk (/steamdata): 3.13 TiB / 3.73 TiB (84%) - btrfs
                                Disk (/satadata): 1.08 TiB / 3.64 TiB (30%) - btrfs
                                Local IP (enp4s0): 192.168.2.106/24 *
                                Locale: en_US.UTF-8

I did try turning off bluetooth and only using the dongle and saw no change in behavior.

No worries. I also wondered if it had something to do with the AMDGPU driver, although that feels like a stretch.

Below is my gpu and driver details, it’s likely more than necessary but let me know if you see any similarities with your setup.

Detailed GPU Driver Info
╭─akat at nasa in ~ 24-06-19 - 17:08:57
╰─○ mhwd
> 0000:03:00.0 (0300:1002:744c) Display controller ATI Technologies Inc:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2024.05.06                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI

╭─akat at nasa in ~ 24-06-19 - 16:56:15
╰─○ lspci -k | grep -EA3 'VGA|3D|Display'
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M] (rev cc)
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 1002
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu
╭─akat at nasa in ~ 24-06-19 - 16:56:47
╰─○ glxinfo | grep OpenGL
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 7900 XT (radeonsi, navi31, LLVM 17.0.6, DRM 3.54, 6.6.32-1-MANJARO)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.0.9-manjaro1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.0.9-manjaro1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.0.9-manjaro1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
╭─akat at nasa in ~ 24-06-19 - 17:05:30
╰─○ pamac search -i vulkan-radeon
lib32-vulkan-radeon  1:24.0.9-1                                                                                                                                                                              multilib
    Open-source Vulkan driver for AMD GPUs - 32-bit
vulkan-radeon  1:24.0.9-1                                                                                                                                                                                       extra
    Open-source Vulkan driver for AMD GPUs
╭─akat at nasa in ~ 24-06-19 - 17:04:45
╰─○ pamac search -i mesa  
libva-mesa-driver  1:24.0.9-1                                                                                                                                                                                   extra
    Open-source VA-API drivers
lib32-mesa-vdpau  1:24.0.9-1                                                                                                                                                                                 multilib
    Open-source VDPAU drivers - 32-bit
lib32-mesa-demos  9.0.0-1                                                                                                                                                                                    multilib
    Mesa demos (32-bit)
lib32-mesa  1:24.0.9-1                                                                                                                                                                                       multilib
    Open-source OpenGL drivers - 32-bit
lib32-libva-mesa-driver  1:24.0.9-1                                                                                                                                                                          multilib
    Open-source VA-API drivers - 32-bit
mesa-vdpau  1:24.0.9-1                                                                                                                                                                                          extra
    Open-source VDPAU drivers
mesa-utils  9.0.0-4                                                                                                                                                                                             extra
    Essential Mesa utilities
mesa-demos  9.0.0-4                                                                                                                                                                                             extra
    Mesa demos
mesa  1:24.0.9-1                                                                                                                                                                                                extra
    Open-source OpenGL drivers

I coulda sworn I have amdgpu-pro installed, guess not.

╭─akat at nasa in ~ 24-06-19 - 17:08:53
╰─○ pamac search -i amdgpu       
xf86-video-amdgpu  23.0.0-2                                                                                                                                                                                     extra
    X.org amdgpu video driver
mhwd-amdgpu  19.1.0-1                                                                                                                                                                                           extra
    MHWD module-ids for amdgpu
╭─akat at nasa in ~ 24-06-19 - 17:17:43
╰─○ sudo dmesg | grep amd
[sudo] password for akat: 
[    2.465957] [drm] amdgpu kernel modesetting enabled.
[    2.466034] amdgpu: Virtual CRAT table created for CPU
[    2.466039] amdgpu: Topology: Add CPU node
[    2.466119] amdgpu 0000:03:00.0: enabling device (0006 -> 0007)
[    2.469364] amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT
[    2.469365] amdgpu: ATOM BIOS: 113-D70401-00
[    2.470060] amdgpu 0000:03:00.0: amdgpu: CP RS64 enable
[    2.470701] amdgpu 0000:03:00.0: [drm:jpeg_v4_0_early_init [amdgpu]] JPEG decode is enabled in VM mode
[    2.514685] amdgpu 0000:03:00.0: vgaarb: deactivate vga console
[    2.514695] amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
[    2.514740] amdgpu 0000:03:00.0: amdgpu: MEM ECC is not presented.
[    2.514742] amdgpu 0000:03:00.0: amdgpu: SRAM ECC is not presented.
[    2.514800] amdgpu 0000:03:00.0: amdgpu: VRAM: 20464M 0x0000008000000000 - 0x00000084FEFFFFFF (20464M used)
[    2.514805] amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
[    2.514809] amdgpu 0000:03:00.0: amdgpu: AGP: 267878400M 0x0000008800000000 - 0x0000FFFFFFFFFFFF
[    2.515345] [drm] amdgpu: 20464M of VRAM memory ready
[    2.515351] [drm] amdgpu: 32067M of GTT memory ready.
[    2.516741] amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware
[    2.730805] amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
[    2.730808] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[    2.730864] amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x004e7d00 (78.125.0)
[    2.730870] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
[    2.896232] amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully!
[    3.438999] amdgpu 0000:03:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
[    3.500112] amdgpu: HMM registered 20464MB device memory
[    3.501581] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[    3.501589] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
[    3.501617] amdgpu: Virtual CRAT table created for GPU
[    3.501701] amdgpu: Topology: Add dGPU node [0x744c:0x1002]
[    3.501702] kfd kfd: amdgpu: added device 1002:744c
[    3.501712] amdgpu 0000:03:00.0: amdgpu: SE 6, SH per SE 2, CU per SH 8, active_cu_number 84
[    3.501873] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[    3.501874] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[    3.501875] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[    3.501875] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[    3.501875] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[    3.501876] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[    3.501876] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[    3.501876] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[    3.501877] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[    3.501877] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[    3.501878] amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[    3.501878] amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
[    3.501878] amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 8
[    3.501879] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 8
[    3.501879] amdgpu 0000:03:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
[    3.504274] amdgpu 0000:03:00.0: amdgpu: Using BACO for runtime pm
[    3.504413] [drm] Initialized amdgpu 3.54.0 20150101 for 0000:03:00.0 on minor 1
[    3.518025] fbcon: amdgpudrmfb (fb0) is primary device
[    3.518027] amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[    9.797890] snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[   12.211885] amdgpu: manual fan speed control should be enabled first
╭─akat at nasa in ~ 24-06-19 - 17:21:03
╰─○ pamac search -i opencl        
ocl-icd  2.3.2-1                                                                                                                                                                                                extra
    OpenCL ICD Bindings
rocm-opencl-runtime  6.0.2-1                                                                                                                                                                                    extra
    OpenCL implementation for AMD
opencl-headers  2:2024.05.08-1                                                                                                                                                                                  extra
    OpenCL (Open Computing Language) header files
Schitzo journal so I can keep track of where I've gone

I just realized it may be a KDE related bug, I can’t say I recall it doing this for the brief time I had it while I was on plasma 5.

I also found this KDE bug that essentially describes the effect of my issue, so it could be related:
466681 – Mouse is lagging/skipping frames when entering Task Manager area

Eventually, that led me to:
Mouse lags when CPU loads - #10 by nate - Plasma - EndeavourOS

That prompted me to panic check if somehow my drives had actually been corrupting themselves, and I got this little nugget:

╭─akat at nasa in ~ 24-06-19 - 17:40:33
╰─○ sudo dmesg | grep error    
[   14.880560] ucsi_ccg 0-0008: error -ETIMEDOUT: PPM init failed

Ah, finally an error! Which turns out means nothing lol:
Are boot time journalctl entries for "ucsi_ccg 0-0008: failed to get FW build information" something to fix or informational? - #2 by megavolt

Ok, back to the EndeavorOS forum, and then onto reddit:
https://www.reddit.com/r/linux_gaming/comments/163n4ey/desktop_lag_after_starting_steam/

Top comment led me here:
After latest Steam beta update (2021-09-29), Steam reinstalled all Proton versions into prefix with appid = 0 · Issue #8114 · ValveSoftware/steam-for-linux · GitHub

Well, I have steam installed, but that issue is not directly related. It did lead me to:
Stuttering when moving mouse with 4000hz polling rate · Issue #1279 · ValveSoftware/gamescope · GitHub

Which mentions:
Mouse polling rate - ArchWiki

So I tried:

╭─akat at nasa in ~ 24-06-19 - 17:56:42
╰─○ sudo evhz
Press CTRL-C to exit.
...
Logitech USB Receiver Mouse: Latest   124Hz, Average   133Hz
Logitech USB Receiver Mouse: Latest   142Hz, Average   133Hz
Logitech USB Receiver Mouse: Latest   125Hz, Average   133Hz
Logitech USB Receiver Mouse: Latest   142Hz, Average   133Hz
Logitech USB Receiver Mouse: Latest   125Hz, Average   133Hz
Logitech USB Receiver Mouse: Latest   142Hz, Average   133Hz
Logitech USB Receiver Mouse: Latest   125Hz, Average   133Hz
Logitech USB Receiver Mouse: Latest   142Hz, Average   133Hz
Logitech USB Receiver Mouse: Latest   125Hz, Average   133Hz
Logitech USB Receiver Mouse: Latest   142Hz, Average   133Hz
Logitech USB Receiver Mouse: Latest   124Hz, Average   133Hz
^C
Average for Logitech USB Receiver Mouse:   133Hz

Ok, now I might be onto something.

So I tried it with wired mouse I mentioned earlier:

...
Logitech G502 HERO Gaming Mouse: Latest   999Hz, Average   999Hz
Logitech G502 HERO Gaming Mouse: Latest  1001Hz, Average   999Hz
Logitech G502 HERO Gaming Mouse: Latest  1000Hz, Average   999Hz
Logitech G502 HERO Gaming Mouse: Latest  1000Hz, Average   999Hz
Logitech G502 HERO Gaming Mouse: Latest   998Hz, Average   999Hz
Logitech G502 HERO Gaming Mouse: Latest  1001Hz, Average   999Hz
Logitech G502 HERO Gaming Mouse: Latest  1001Hz, Average   999Hz
Logitech G502 HERO Gaming Mouse: Latest   999Hz, Average   999Hz
^C
Average for Logitech G502 HERO Gaming Mouse:   999Hz

So the tool for the one mouse did read the polling rate correctly.

MX Master 3s is supposed to have a polling rate of 125hz, so I’m not sure what the jumps from 124Hz to 142Hz and back is about.

Turns out, normal:
https://www.reddit.com/r/MouseReview/comments/vi4ujl/comment/jsbkams

People in that thread mention RF interference, makes sense. So I started reading up on that.
Came across this post:
Wireless mouse random hesitation, lag, and irritations ja-ja-ja-jitters... - #10 by ianadams2 - Hardware - Spiceworks Community

People in here are really confident it’s a RF issue.

So, I start looking around for a way to diagnose this. Surely, in some obscure corner of the internet someone has to have done that.

Of course, as all things do, it led me back to the Arch wiki forums.
How do I diagnose mouse lag/stuttering ? / Newbie Corner / Arch Linux Forums

One of the posts mentions hardware interference, so I looked around and found this:
[SOLVED] Laggy, sticky mouse input / Kernel & Hardware / Arch Linux Forums

Which mentions this:
Power management - ArchWiki

╭─akat at nasa in ~ 24-06-19 - 18:21:16
╰─○ systool -v -m usbcore
Module = "usbcore"

  Attributes:
    uevent              = <store method only>

  Parameters:
    authorized_default  = "-1"
    autosuspend         = "2"
...

Well, now I have something to try at least.

So I just read this

From the introduction:

The purpose of this document is to create an awareness of radio frequency
interference to wireless devices operating in the 2.4 GHz ISM band as a result of
certain USB 3.0* devices and cables. This is a guide to customers of the USB 3.0 RFI
mitigation options that are available.

From section 3.2:

In this paper, an example of a wireless mouse communicating to a notebook computer
through an associated USB2 wireless dongle is used to demonstrate the impact of the
USB 3.0 noise on wireless device performance. The test setup, shown in Figure 3-4,
was used. An external USB 3.0 hard drive was connected to the USB 3.0 port on the
notebook computer using a 3-foot USB 3.0 cable. On an adjacent USB2 port, the
wireless mouse dongle was connected.

I have a ****ton of USB3.0 crap near my dongle. I’ve also had USB3.0 devices near it at times as well.

And wouldn’t you know, Bolt (the BLE protocol Logitech uses for the MX Master 3S), uses the 2.4Ghz band.

For my setup, this seems really promising. I’ll muck around with this and see if I can do anything consistently. I can’t say for sure but I have a theory as to why it has only happened on Manjaro for me.

Does your laptop use any USBC/USB3.0 devices?

If not, does your laptop use 2.4 Ghz for wifi? Perhaps there’s something to look into there.
From the usb.org paper again:

As shown in Table 3-1, there is degradation in the performance of the wireless mouse
when a USB 3.0 device is connected to the notebook computer. At a distance of 3 feet
and greater away from the notebook computer, a significant lag was experienced in
the response of the mouse. The impact to mouse performance was found to be the
same whether the USB 3.0 peripheral device had data being actively written to it or if
it was merely connected to the notebook computer and the link to it established.
A similar impact to wireless mouse performance was noted if a USB 3.0 device, such
as a flash drive, was used. Since the noise from the USB 3.0 is broadband, it could
potentially impact any radio whose antenna is close by. Although the test results are
not shown in this paper, similar impact was seen to Bluetooth radio performance.

I speak from personal experience, but indeed the same symptoms can have different causes.

When the cursor flickers or stutters it has been a signal problem, either due to interference or the device trying to reconnect.

When the cursor appears and disappears elsewhere when moving the mouse, it is a video synchronization problem.

Just try with a wired mouse, if the cursor keeps jumping the origin is in the video synchronization or in any case the problem is not the mouse. However, this does not mean that it is the fault of the signal.

DDC utilities to set monitor parameters (ddcutil, ddccontrol, …) can cause this problem, the following command reads the monitor brightness every second:

watch ddcutil -d 1 getvcp 10

Executing it may reproduce the cursor jumping bug on the screen.

Thanks for the thorough investigation, it is quite interesting.
It is specially the case if a non-USB3 cable is used, or a non-shielded one. That is quite easy to understand, USB3 bandwidth is rather wide and high-frequency.
I haven’t read the paper yet. Do they compare different cables? And maybe also different decies?

I normally have no USB3 storage connected to my desktop and one USB3 hub. But again, why it gives problem only with one OS? If the signal is corrupted between the mouse and the receiver (being it the dongle or the BT antenna) I don’t really see how the OS can have an impact.

Now “on the road”, on my laptop now I have nothing connected, except the mouse via BT.

EDIT: forgot to mention that on the desktop the WiFi is disabled (in the BIOS). One the laptop, however, I am connected using a 2.4 GHz WiFi. So according to your findings that could be something to look into. But the mouse signal is so simple and low data that it is very very robust to interference. In other words, if the mouse signal is affected by a WiFi, then just having 3 or 4 devices connected to the same WiFi would make their connection unusable.

In general, laptops have the wifi antenna around the screen.

Ok, an interesting new finding is that, at least in this laptop, the issue may be more generally related to BT drivers.
I’ve connected BT headphones and they perform terribly. Not talking about music quality or something… the sound is stuttering, breaking-up etc…

So yeah, there is definitely something wrong in the BT here. At this point, since this laptop has no dual boot, I can say if it’s the BT device that is broken or something in the OS/SW. I may try with a Live USB once I have a minute.

Helo @akat :wink:

File: /etc/tlp.d/40-custom.conf

USB_EXCLUDE_BTUSB=1

Then run: sudo tlp usb

Radio Devices: Bluetooth, Wi-Fi, WWAN — TLP 1.6.1 documentation

That should disable power saving on bluetooth devices.

1 Like

Hey, it’s the legend themself! Thanks for the suggestion, although I think this is more suited for @billznn maybe, since I don’t use TLP.

I’ll be giving this a shot as soon as I have time, same thing different method:

I would’ve done it already but I would like to just disable autosuspend/power saving outright, still gotta figure that out :slight_smile:

Edit: The forum wants me to just make one post instead of two.

Yes, I remember reading about their tests with storage devices and a mouse. I don’t recall if they tested shielded/unshielded USB3.0 cables though. Frankly, I’m not sure I even know what that means in the context of USB from a technical perspective :yum:

Here are some excerpts from section 4 of the USB org paper:

As previously described in Section 3.1, noise due to the USB 3.0 data spectrum can
radiate from a USB 3.0 peripheral device and its connector. Properly shielding the
USB 3.0 peripheral device can help reduce the amount of noise emitted in the 2.4 GHz
band. To illustrate this point, different areas of an external HDD were shielded, and for
each case, noise emitted into the 2.4 GHz band was measured. The test setup used
for this measurement is the same as in Figure 3-2.

In addition to radiation from the USB 3.0 peripheral device, noise can radiate from the
USB 3.0 receptacle connector on a PC platform. As an example, to measure the level
of noise due to the USB 3.0 notebook connector, the test setup, shown in Figure 4-3,
was used. A near field probe was placed near the USB 3.0 connector on Notebook ‘A’,
in an RF absorber box. To minimize any radiation contribution from the peripheral
device, it was fully shielded and placed away from Notebook ‘A’ using a 6-foot USB 3.0
cable.

This had no effect whatsoever on my issue.
Still identical to before:

  • headphones still breaking up and stuttering, impossible to use more or less (tried 2 different ones that work on a Win laptop); same for the microphone integrates in the same headset, tried with a couple of trial calls
  • mouse still… how I can describe… the absolute opposite of smooth, impossible to be precise basically (also here, tried on a Win laptop one the very same surface)

I start to suspect it is the BT driver/the kernel for this very particular laptop, maybe…

@billznn

zcat /proc/config.gz | grep "CONFIG_BT_HCIBTUSB_AUTOSUSPEND"

If y then add: btusb.enable_autosuspend=0 to the kernel parameters.

USB Devices — TLP 1.6.1 documentation

sudo tlp-stat --usb

Usually the BT device should be on here, not auto, if suspending is disabled.

Hey thanks a lot for the super quick reply!
The output of zcat... was indeed y so I’ve added the parameter to the kernel (setting it in GRUB).
This seems to have fixed the issue with the headphones, they seem to be working smooth now.

However, somehow the mouse behaviour is still not convincing. To be honest, I’m not sure if it is only an impression now, it seems improved, but at times it still stutters…
Which somehow brings back to the very original topic…

I’ll try now to do some of the photo-editing that made me noticing at first how bad the mouse was, so I can recalibrate my impressions maybe…

What’s “dull”? LEDs? Movement? It’s become boring? :man_shrugging:

How old is it? The switches eventually wear out, and when they do, they tend to exhibit one or more of the following behaviours.

  1. Intermittently not trigger, as you describe.
  2. Trigger more than once when pressed.
  3. Trigger randomly without interaction.

I’ve only seen number 3 on TVs and monitors so far, they tend to use tactile switches and mice tend to use microswitches, but some mice use tactile.

Test on another computer and/or OS if possible…make sure you use it long enough to see if it happens. If it happens everywhere, especially if it happens on another OS, then it’s very likely to be the mouse.

If you have the skills and tools you can probably replace the switches if you want, otherwise replace the mouse.

In future, it’s best to open your own thread. :slight_smile:

1 Like

For me, it seems it was at least in part RF interference. My DAC started picking up RF interference. I thought it was dying at first, but it sounded strangely akin to dial up, so I googled. Three videos of a very similar sound later, I threw my phone out of the room exclaiming “Aha!”. That didn’t resolve it, so I started to move my stack to see if I had a loose cable or something and slightly shifted some of the cables near it in the process. Immediately after shifting those usb3/thunderbolt cables near it, silence. Then it hit me, they were coiled.

Since I shifted those cables, it’s all stopped. Mouse and DAC issues alike.

It’s been about a two days without so much as a stutter. If this keeps through the weekend, I’m going to consider my issue resolved.

FWIW, I had btusb autosuspend disable before I made my first post IIRC. I don’t recall why. Even though it seems to be resolved, I’ve since added USB-Autosuspend, just in case:

GRUB_CMDLINE_LINUX_DEFAULT="... btusb.enable_autosuspend=0  usbcore.autosuspend=-1"
2 Likes