From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 219332] /sys/devices/system/cpu/cpufreq/policy0/energy_performance_preference: Device or resource busy
Date: Sun, 29 Sep 2024 19:29:15 +0000 [thread overview]
Message-ID: <bug-219332-137361-IXkEwtfrc7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219332-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219332
--- Comment #5 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
Can you please provide a kernel log with dynamic debugging turned on for
drivers/cpufreq/amd-pstate.c so I can understand what it is doing with your
hardware?
Just a guess with no messages but it's very possible that because 6.11 doesn't
have c3e093efbc6cac7bf9dc531dcb751b86daaa65b0 an error is being masked.
Perhaps you can try to add that commit and see if it changes?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-09-29 19:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 13:13 [Bug 219332] New: /sys/devices/system/cpu/cpufreq/policy0/energy_performance_preference: Device or resource busy bugzilla-daemon
2024-09-29 13:14 ` [Bug 219332] " 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 [this message]
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-IXkEwtfrc7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).