Fedora44 KDE sporatic system freezes appear to be related to Powerdevil?

After reducing system freezes by 90% caused previously by a Widged: Panel Colorizer it still happens at least once a day kind of out of the blue.

At the time of the freeze at around 07:30AM this morning and after reboot, this is what I found in the journal:

journalctl -b -0 -p err --no-pager
Jul 30 17:28:32 fedora kernel: virt/tdx: TDX not supported by the host platform
Jul 30 17:28:32 fedora kernel: platform MSFT0201:00: AMD-Vi: [Firmware Bug]: No ACPI device matched UID, but 1 device matched HID.
Jul 30 17:28:33 fedora kernel: amdtee: failed to load firmware /amdtee/f29bb3d9-bd66-5441-afb88acc2b2b60d6.bin
Jul 30 17:28:33 fedora kernel: amdtee: failed to copy TA binary
Jul 30 17:28:33 fedora kernel: Failed to open TEE session err:0x0, rc:-12
Jul 30 17:28:33 fedora kernel: amd-pmf AMDI0103:00: Failed to open TA session (-12)
Jul 30 17:28:33 fedora kernel: hid-multitouch 0018:093A:0274.0003: Returned feature report did not match the request
Jul 30 17:28:34 fedora kernel: ucsi_acpi USBC000:00: unknown error 256
Jul 30 17:28:35 fedora kernel: ucsi_acpi USBC000:00: unknown error 256
Jul 30 07:28:39 fedora bluetoothd[1126]: Failed to set mode: Failed (0x03)
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error(s) opening ddc devices
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-3
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-4
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-5
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-6
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-7
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-8
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-9
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-10
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-11
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-12
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-13
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-14
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-15
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-16
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-17
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-18
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-19
Jul 30 07:28:50 fedora org_kde_powerdevil[2324]: [  2324] Error EACCES(-13): Permission denied opening /dev/i2c-20
Jul 30 07:28:51 fedora bluetoothd[1126]: Failed to set mode: Failed (0x03)

All looks pretty normal to me - are you concerned about the permission denied talking to those i2c devices?

Do you actually have any monitors plugged in which have their brightness controlled via DDC, and it’s not working?

Yes. It’s the only part I could see which might be responsible for these system freezes.

No, just the Laptop by itself, no other peripherals attached.

I get many of the same messages, which could do with being suppressed I suspect, when powerdevil tries to talk to the i2c bus for devices which aren’t plugged in. Talking to /dev/i2c-9, works as expected as there’s a monitor attached to it, as you can see from the DDCA event.

A quick grep of my journal logs for /dev/i2c shows the following and I have no issues because of the failures to talk to the empty, unconnected devices.

Sep 29 20:57:48 lurcher org_kde_powerdevil[2372]: [  2372] Device /dev/i2c-0 lacks R/W permissions
Sep 29 20:57:49 lurcher org_kde_powerdevil[2372]: Error EACCES(-13): Permission denied opening /dev/i2c-0
Sep 29 20:57:49 lurcher org_kde_powerdevil[2372]: [  2372] Error EACCES(-13): Permission denied opening /dev/i2c-0
Sep 30 08:56:36 lurcher org_kde_powerdevil[2372]: [  2536] Device /dev/i2c-0 lacks R/W permissions
Sep 30 08:56:37 lurcher org_kde_powerdevil[2372]: [  2536] Device /dev/i2c-0 lacks R/W permissions
Sep 30 08:56:37 lurcher org_kde_powerdevil[2372]: [  2536] Emitting DDCA_Display_Status_Event[43129.251:  DDCA_EVENT_DISPLAY_DISCONNECTED, card1-DP-4, dref: DDCA_Display_Ref[1], io_path:/dev/i2c-9, ddc working: false]
Sep 30 08:56:37 lurcher org_kde_powerdevil[2372]: [  9811] Invoking callback function 0x7fe0eb081af0 for event DDCA_Display_Status_Event[43129.251:  DDCA_EVENT_DISPLAY_DISCONNECTED, card1-DP-4, dref: DDCA_Display_Ref[1], io_path:/dev/i2c-9, ddc working:>
Sep 30 08:56:37 lurcher org_kde_powerdevil[2372]: [  9811] Callback function 0x7fe0eb081af0 for event DDCA_Display_Status_Event[43129.251:  DDCA_EVENT_DISPLAY_DISCONNECTED, card1-DP-4, dref: DDCA_Display_Ref[1], io_path:/dev/i2c-9, ddc working: false] c>
Sep 30 08:56:51 lurcher org_kde_powerdevil[2372]: [  2536] Device /dev/i2c-0 lacks R/W permissions
Sep 30 08:56:52 lurcher org_kde_powerdevil[2372]: [  2536] Emitting DDCA_Display_Status_Event[43144.419:  DDCA_EVENT_DISPLAY_CONNECTED, card1-DP-4, dref: DDCA_Display_Ref[2], io_path:/dev/i2c-9, ddc working: true]
Sep 30 08:56:52 lurcher org_kde_powerdevil[2372]: [  9840] Invoking callback function 0x7fe0eb081af0 for event DDCA_Display_Status_Event[43144.419:  DDCA_EVENT_DISPLAY_CONNECTED, card1-DP-4, dref: DDCA_Display_Ref[2], io_path:/dev/i2c-9, ddc working: tr>
Sep 30 08:56:52 lurcher org_kde_powerdevil[2372]: [  9840] Callback function 0x7fe0eb081af0 for event DDCA_Display_Status_Event[43144.419:  DDCA_EVENT_DISPLAY_CONNECTED, card1-DP-4, dref: DDCA_Display_Ref[2], io_path:/dev/i2c-9, ddc working: true] compl>
Sep 30 08:56:53 lurcher org_kde_powerdevil[2372]: [  2372] Device /dev/i2c-0 lacks R/W permissions
Sep 30 08:56:54 lurcher org_kde_powerdevil[2372]: Error EACCES(-13): Permission denied opening /dev/i2c-0
Sep 30 08:56:54 lurcher org_kde_powerdevil[2372]: [  2372] Error EACCES(-13): Permission denied opening /dev/i2c-0
Oct 01 08:42:29 lurcher org_kde_powerdevil[2372]: [  9842] Device /dev/i2c-0 lacks R/W permissions
Oct 01 08:42:29 lurcher org_kde_powerdevil[2372]: [  9842] Device /dev/i2c-0 lacks R/W permissions

If you’re interested in testing I built the updated version of ddcutil in a copr.

Thanks