Micro stuttering every few seconds; issues with Powerdevil failing

[StellaeAlis]

I’ve been using Garuda for a while now and I’m pretty happy with it overall, but there’s this stuttering every few seconds that freezes all monitors for about one second. I’ve already tried a few things like changing the kernel and upgrading the BIOS, but nothing changed.

Today I found these error messages when doing journalctl -b -p3 -e -f. They start just after the PC finished booting and continue every few seconds until it shuts down.

Jan 06 23:20:15 draco libddcutil[239916]: i2c_check_businfo_connector() failed for bus 9
Jan 06 23:20:17 draco systemd[4283]: Failed to start Powerdevil.
Jan 06 23:20:20 draco libddcutil[241160]: i2c_check_businfo_connector() failed for bus 9
Jan 06 23:20:23 draco systemd[4283]: Failed to start Powerdevil.
Jan 06 23:20:26 draco libddcutil[241189]: i2c_check_businfo_connector() failed for bus 9
Jan 06 23:20:28 draco systemd[4283]: Failed to start Powerdevil.
Jan 06 23:20:31 draco libddcutil[241221]: i2c_check_businfo_connector() failed for bus 9
Jan 06 23:20:34 draco systemd[4283]: Failed to start Powerdevil.
Jan 06 23:20:37 draco libddcutil[241251]: i2c_check_businfo_connector() failed for bus 9
Jan 06 23:20:39 draco systemd[4283]: Failed to start Powerdevil.
Jan 06 23:20:42 draco libddcutil[242494]: i2c_check_businfo_connector() failed for bus 9
Jan 06 23:20:45 draco systemd[4283]: Failed to start Powerdevil.

I checked these errors against the freezing and it matches perfectly. Just after every freeze a new i2c_check_businfo_connector() failed for bus 9 error shows up. I’m not sure if the other error is connected to the freezes, but it doesn’t seem so.

Of course I tried looking up this error, but I didn’t find anything useful, here or on Google. Is there any way for me to fix this problem?

System:
  Kernel: 6.1.70-1-lts arch: x86_64 bits: 64 compiler: gcc v: 13.2.1 clocksource: tsc
    available: hpet,acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
    root=UUID=8a635b38-79b3-418b-914f-15d084f0d99c rw rootflags=subvol=@ quiet quiet
    rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=b9b675f9-5204-45ce-ac23-53e1467b7322 loglevel=3 ibt=off
  Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2 dm: SDDM
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ROG MAXIMUS XI CODE v: Rev 1.xx serial: <superuser required>
    UEFI: American Megatrends v: 1802 date: 12/01/2020
Battery:
  Device-1: ps-controller-battery-48:18:8d:42:e1:f1 model: N/A serial: N/A charge: N/A
    status: charging
CPU:
  Info: model: Intel Core i9-9900K bits: 64 type: MT MCP arch: Coffee Lake gen: core 9 level: v3
    note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xD (13)
    microcode: 0xFA
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
    desc: d-8x32 KiB; i-8x32 KiB L2: 2 MiB desc: 8x256 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 4700 high: 4701 min/max: 800/5000 scaling: driver: intel_pstate
    governor: powersave cores: 1: 4700 2: 4700 3: 4700 4: 4700 5: 4700 6: 4701 7: 4700 8: 4700
    9: 4700 10: 4700 11: 4700 12: 4700 13: 4700 14: 4700 15: 4700 16: 4700 bogomips: 115232
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: HDMI-A-1 empty: none
    bus-ID: 00:02.0 chip-ID: 8086:3e98 class-ID: 0300
  Device-2: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] vendor: ASUSTeK driver: nvidia v: 545.29.06
    alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current (as of 2023-10; EOL~2026-12-xx)
    arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie: gen: 3 speed: 8 GT/s
    lanes: 16 ports: active: none off: DP-1, DP-2, HDMI-A-2, HDMI-A-3 empty: Unknown-1
    bus-ID: 01:00.0 chip-ID: 10de:1e07 class-ID: 0300
  Device-3: Logitech BRIO 4K Stream Edition driver: snd-usb-audio,uvcvideo type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4:4 chip-ID: 046d:086b class-ID: 0102
    serial: <filter>
  Device-4: Valve 3D Camera driver: uvcvideo type: USB rev: 3.2 speed: 5 Gb/s lanes: 1
    mode: 3.2 gen-1x1 bus-ID: 2-3.1:4 chip-ID: 28de:2400 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.10 with: Xwayland v: 23.2.3 compositor: kwin_x11 driver: X:
    loaded: modesetting,nvidia dri: iris gpu: i915,nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 8120x2580 s-dpi: 96 s-size: 2148x682mm (84.57x26.85")
    s-diag: 2254mm (88.73")
  Monitor-1: DP-1 mapped: DP-0 note: disabled model: Nvidia built: 1990 size-res: N/A gamma: 1.2
    modes: 640x480
  Monitor-2: DP-2 note: disabled pos: primary,bottom-c model: Samsung LC49G95T serial: <filter>
    built: 2020 res: 5120x1440 dpi: 130048 gamma: 1.2 size: 1x1mm (0.04x0.04") diag: 1239mm (48.8")
    modes: max: 2560x1440 min: 640x480
  Monitor-3: HDMI-A-1 mapped: HDMI-0 pos: middle-l model: Acer GN246HL serial: <filter>
    built: 2016 res: 1080x1920 hz: 60 dpi: 92 gamma: 1.2 size: 299x531mm (11.77x20.91")
    diag: 609mm (24") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  Monitor-4: HDMI-A-2 mapped: HDMI-1 note: disabled pos: top-center model: VG245 serial: <filter>
    built: 2017 res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2 size: 595x336mm (23.43x13.23")
    diag: 609mm (24") ratio: 16:9 modes: max: 1920x1080 min: 640x480
  Monitor-5: HDMI-A-3 mapped: HDMI-1-1 note: disabled pos: bottom-r model: Acer Z271
    serial: <filter> built: 2016 res: 1920x1080 hz: 60 dpi: 92 gamma: 1.2
    size: 531x299mm (20.91x11.77") diag: 683mm (26.9") ratio: 16:9 modes: max: 1920x1080
    min: 640x480
  API: EGL v: 1.5 hw: 
drv: intel iris drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: iris device: 3 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 545.29.06 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 memory: 10.74 GiB
  API: Vulkan v: 1.3.274 layers: 8 device: 0 type: integrated-gpu name: Intel UHD Graphics 630
    (CFL GT2) driver: mesa intel v: 23.3.2-arch1.2 device-ID: 8086:3e98 surfaces: xcb,xlib
    device: 1 type: discrete-gpu name: NVIDIA GeForce RTX 2080 Ti driver: nvidia v: 545.29.06
    device-ID: 10de:1e07 surfaces: xcb,xlib device: 2 type: cpu name: llvmpipe (LLVM 16.0.6 256
    bits) driver: mesa llvmpipe v: 23.3.2-arch1.2 (LLVM 16.0.6) device-ID: 10005:0000
    surfaces: xcb,xlib
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
  Device-2: NVIDIA TU102 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f7 class-ID: 0403
  Device-3: YUAN High-Tech Development vendor: Corsair Memory driver: N/A pcie: gen: 2
    speed: 5 GT/s lanes: 2 link-max: lanes: 4 bus-ID: 02:00.0 chip-ID: 12ab:0710 class-ID: 0480
  Device-4: Valve VR Radio driver: cdc_acm,hid-generic,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-3.3.2:9 chip-ID: 28de:2102 class-ID: 0a00 serial: <filter>
  Device-5: Valve VR Radio & HMD Mic driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-3.3.3:12 chip-ID: 28de:2102 class-ID: 0102
    serial: <filter>
  Device-6: Logitech BRIO 4K Stream Edition driver: snd-usb-audio,uvcvideo type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4:4 chip-ID: 046d:086b class-ID: 0102
    serial: <filter>
  Device-7: Sony DualSense wireless controller (PS5) driver: playstation,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:6 chip-ID: 054c:0ce6
    class-ID: 0300
  Device-8: SteelSeries ApS Arctis Pro Wireless driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-8.3.3:23 chip-ID: 1038:1294
    class-ID: 0300
  API: ALSA v: k6.1.70-1-lts status: kernel-api tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.0 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 Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel bus-ID: 00:14.3
    chip-ID: 8086:a370 class-ID: 0280
  IF: wlo1 state: down mac: <filter>
  Device-2: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
  IF: eno2 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-3: Sony DualSense wireless controller (PS5) driver: playstation,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:6 chip-ID: 054c:0ce6
    class-ID: 0300
  IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: <filter>
  IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:21 chip-ID: 8087:0aaa class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.1 lmp-v: 10 status:
    discoverable: no pairing: no class-ID: 7c0104
Drives:
  Local Storage: total: 6.37 TiB used: 544.65 GiB (8.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  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: 37.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXE7 temp: 36.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000VN008-2DR166 size: 3.64 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5980 serial: <filter>
    fw-rev: SC60 scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: ASUS model: Tek ROG RYUJIN size: 4 MiB block-size:
    physical: 4096 B logical: 4096 B type: USB rev: 2.0 spd: 12 Mb/s lanes: 1 mode: 1.1 tech: N/A
    serial: <filter> fw-rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 1.79 TiB size: 1.79 TiB (100.00%) used: 544.65 GiB (29.8%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 588 KiB (0.2%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 1.79 TiB size: 1.79 TiB (100.00%) used: 544.65 GiB (29.8%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 1.79 TiB size: 1.79 TiB (100.00%) used: 544.65 GiB (29.8%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 1.79 TiB size: 1.79 TiB (100.00%) used: 544.65 GiB (29.8%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 34.31 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3
  ID-2: swap-2 type: zram size: 31.19 GiB used: 0 KiB (0.0%) priority: 100 comp: zstd
    avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 45.0 C mobo: N/A gpu: nvidia temp: 43 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 34%
Info:
  Processes: 452 Uptime: 45m wakeups: 0 Memory: total: 32 GiB available: 31.19 GiB
  used: 9.08 GiB (29.1%) Init: systemd v: 255 default: graphical tool: systemctl Compilers:
  gcc: 13.2.1 clang: 16.0.6 Packages: pm: pacman pkgs: 1627 libs: 492 tools: octopi,paru
  Client: shell wrapper v: 5.2.21-release inxi: 3.3.31
Garuda (2.6.22-1):
  System install date:     2023-09-01
  Last full system update: 2024-01-03
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            

[Kayo]

@StellaeAlis

I’ve already tried a few things like changing the kernel and upgrading the BIOS, but nothing changed.

@StellaeAlis

 Mobo: ASUSTeK model: ROG MAXIMUS XI CODE v: Rev 1.xx serial: <superuser required>
    UEFI: American Megatrends v: 1802 date: 12/01/2020

Latest BIOS should be v2004 dated 2021/11/29. I would be sure to be on the latest version as it noted to “Improve system stability”.

ROG MAXIMUS XI CODE | Motherboards | ROG Global

If that doesn’t help by itself, what was the other kernels you have tried?

[StellaeAlis]

@Kayo

Latest BIOS should be v2004 dated 2021/11/29.

You’re right! I just used the integrated BIOS updater and it told me that I’m already using the newest version. I’ll try v2004 in a moment.

The kernels I’ve tried are linux, linux-zen and I’m currently using linux-lts.

[StellaeAlis]

I just updated my BIOS to v2004 manually, but it didn’t change anything regarding the freezes or errors

[Kayo]

@StellaeAlis

i2c_check_businfo_connector() failed for bus 9

For clarification, has this problem been ongoing since you have first running Garuda?
Also, since your garuda-inxi hinted at Windows; have you noticed any odd issues that would seem like random stutters if you are using that?

I ask because I2C issues could be pointing to a hardware issue now that kernel and BIOS are ruled out.

[StellaeAlis]

The freezes have been an ongoing problem, but I discovered this error message for the first time today, so I can’t say.

I have Windows 10 installed on a completely separate drive and I’ve never had any issues in Windows. Do you think it might be a problem with the drive Garuda is installed on?

[Kayo]

I can’t say for certain, but it could be a possibility… or at least one microcontroller used for that specific bus. Things related to I2C is rather extensive I²C - Wikipedia .
I would be sure to test those three kernels on the new BIOS just to be on the safe side and see if those errors pop up again. (if you haven’t already of course)

Another possibility is that I2C check issue is unrelated to your stutters; there could be an issue more centered around Powerdevil and the constant failures of it starting is causing your stutters. (Or more of a certainty if checking other kernels the I2C check issue stopped but Powerdevil still failed to start.)
You could do a quick test to see if setting a mask for it from blocking it from starting up would help the stutters go away (be sure to restart after)

systemctl --user mask plasma-powerdevil.service

(You can use unmask instead of mask in that command later to bring back that service. Be sure to restart yet again.)

[StellaeAlis]

@Kayo

systemctl --user mask plasma-powerdevil.service

That fixed it! Both errors as well as the stutters completely disappeared!

Is there any disadvantage to keeping it like that or is there maybe a fix for powerdevil?

[Kayo]

Well, of course you wouldn’t be able to use power management provided by powerdevil Power Management

@StellaeAlis

is there maybe a fix for powerdevil?

I assume it is related to this bug report 476375 – Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
Hopefully it will be fixed in one way or the other soon.

[StellaeAlis]

I unmasked powerdevil again and downgraded it and ddcutil to the version mentioned in the bug report. Now it works as expected. I’ll keep an eye on the report to see when I can update them again.

Thank you very much for your help!

[Kayo]

Thank you for being so detailed in your issue reporting. It was a pleasure.
Welcome to the forums by the way

[daveschz]

Grateful for this post, i just updated today and ddcutil was upgraded to 2.1.0-3. Had this microstuttering and the errors in journalctl logs you mentioned. Downgraded to 2.1.0-2 and the stuttering went away. Looks like 2.1.0-3 broke it again (there’s a new comment on the BBS page).