Bug 433868 - PowerDevil with ACPI resource mode lax causes generates issues with AMDPU
Summary: PowerDevil with ACPI resource mode lax causes generates issues with AMDPU
Status: REPORTED
Alias: None
Product: Powerdevil
Classification: Plasma
Component: general (show other bugs)
Version: 5.21.2
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-02 18:39 UTC by Ricardo Steijn
Modified: 2023-09-24 23:58 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
errors caused by powerdevil running on the setting "acpi_enforce_resources=lax" (29.54 KB, text/plain)
2021-03-02 18:39 UTC, Ricardo Steijn 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ricardo Steijn 2021-03-02 18:39:28 UTC 
Created attachment 136328 [details]
errors caused by powerdevil running on the setting "acpi_enforce_resources=lax"

SUMMARY
Setting "acpi_enforce_resources=lax" causes powerdevil to conflict with other devices. In my case it was with AMDGPU and CPU. Resource mode "lax" is used to be able to access the SMbus controller.

This bug is posted for PowerDevil as uninstalling it resolves the errors.

STEPS TO REPRODUCE
1. Set "acpi_enforce_resources=lax" as kernel parameter
2. Check journal for AMDGPU (dmesg | grep amdgpu)
3. 

OBSERVED RESULT
Repetitive error messages in journal for AMDGPU while PowerDevil is installed and active. No more errors when PowerDevil uninstalled.


EXPECTED RESULT
Setting "acpi_enforce_resources=lax" is not uncommon, so i would expect it to not cause extra issues. I could however be wrong, if setting it to lax is known to produce unexpected behaviour, then this bug can be closed. I decided to report it anyway in case it actually is a bug.


SOFTWARE/OS VERSIONS
Software: Arch Linux x86_64
Kernel: 5.11.2-zen1-1-zen
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Maugre 2021-03-03 20:17:49 UTC 
I'm experiencing these same messages in dmesg. Whatever the cause also messes with my ability to set GPU clocks or get any temperature/fan speed information from amdgpu.

Resolved by removing powerdevil package or reverting powerdevil to 5.21.0.r2408.g1aba3c6b-1 (not necessarily the last 'good' version) so definitely seems to be powerdevil triggering something with amdgpu and i2c.

Possibly related issue in amdgpu: https://gitlab.freedesktop.org/drm/amd/-/issues/1470
Comment 2 Maugre 2021-03-03 21:21:08 UTC 
Testing manjaro packages I have locally, something broke between .0 and .1. Looking at the git log for 5.21 branch, the only significant change since .0 was d1bf7bfc. I suspect whatever that does is triggering this i2c issue in amdgpu.
Comment 3 K900 2021-03-23 13:29:14 UTC 
AFAICT Powerdevil doesn't actually do any I2C accesses by itself, but it does call ddcutil, which does. Filed a ddcutil issue: https://github.com/rockowitz/ddcutil/issues/194
Comment 4 Nate Graham 2023-09-01 16:29:37 UTC 
Is this still an issue with the latest kernel and ddcutil?