From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 219332] New: /sys/devices/system/cpu/cpufreq/policy0/energy_performance_preference: Device or resource busy
Date: Sun, 29 Sep 2024 13:13:10 +0000 [thread overview]
Message-ID: <bug-219332-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219332
Bug ID: 219332
Summary: /sys/devices/system/cpu/cpufreq/policy0/energy_perform
ance_preference: Device or resource busy
Product: Power Management
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: high
Priority: P3
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: aros@gmx.com
Regression: No
Created attachment 306935
--> https://bugzilla.kernel.org/attachment.cgi?id=306935&action=edit
A dump of /sys/devices/system/cpu
I've played with various tee: /sys/devices/system/cpu/cpufreq/policy0/* options
and now on Linux 6.11 and Ryzen 7 5800X I'm getting this:
perfbias.sh power
Now: performance
Switching to: power
tee: /sys/devices/system/cpu/cpufreq/policy0/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy10/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy11/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy12/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy13/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy14/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy15/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy1/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy2/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy3/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy4/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy5/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy6/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy7/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy8/energy_performance_preference:
Device or resource busy
tee: /sys/devices/system/cpu/cpufreq/policy9/energy_performance_preference:
Device or resource busy
Result: performance
This doesn't seem right.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2024-09-29 13:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 13:13 bugzilla-daemon [this message]
2024-09-29 13:14 ` [Bug 219332] /sys/devices/system/cpu/cpufreq/policy0/energy_performance_preference: Device or resource busy bugzilla-daemon
2024-09-29 13:24 ` bugzilla-daemon
2024-09-29 13:50 ` bugzilla-daemon
2024-09-29 19:18 ` bugzilla-daemon
2024-09-29 19:29 ` bugzilla-daemon
2024-09-30 5:53 ` bugzilla-daemon
2024-09-30 13:28 ` bugzilla-daemon
2024-09-30 15:50 ` bugzilla-daemon
2024-09-30 16:11 ` bugzilla-daemon
2024-09-30 17:04 ` bugzilla-daemon
2024-09-30 17:15 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-219332-137361@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-pm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.