From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 216248] New: [Regression] amd-pstate stops working after [ACPI: CPPC: Check _OSC for flexible address space]
Date: Thu, 14 Jul 2022 20:40:31 +0000 [thread overview]
Message-ID: <bug-216248-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216248
Bug ID: 216248
Summary: [Regression] amd-pstate stops working after [ACPI:
CPPC: Check _OSC for flexible address space]
Product: Power Management
Version: 2.5
Kernel Version: 5.18.11
Hardware: AMD
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: arek.rusi@gmail.com
Regression: No
Created attachment 301428
--> https://bugzilla.kernel.org/attachment.cgi?id=301428&action=edit
lscpu
Model name: AMD Ryzen 7 5800HS with Radeon Graphics
CPU family: 25
Model: 80
Flags: ... cppc ...
amd-pstate won't load:
modprobe: ERROR: could not insert 'amd_pstate': No such device
first bad commit is: 13bb696dd2f3bd5f23a6be2d97063ee3bdb6b690
[ACPI: CPPC: Check _OSC for flexible address space]
it cannot be simlpy reverted unfortunaltelly
Issue is quite simmilar to:
https://lore.kernel.org/lkml/3559249.JlDtxWtqDm@natalenko.name/
To be sure i've tweaked that patch to fit to my cpu, but it didn't work.
--
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:[~2022-07-14 20:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 20:40 bugzilla-daemon [this message]
2022-07-14 20:45 ` [Bug 216248] [Regression] amd-pstate stops working after [ACPI: CPPC: Check _OSC for flexible address space] bugzilla-daemon
2022-07-15 3:12 ` bugzilla-daemon
2022-07-15 3:20 ` bugzilla-daemon
2022-07-15 8:09 ` bugzilla-daemon
2022-07-15 8:11 ` bugzilla-daemon
2022-07-15 8:12 ` bugzilla-daemon
2022-07-15 8:56 ` bugzilla-daemon
2022-07-15 9:20 ` bugzilla-daemon
2022-07-15 9:21 ` bugzilla-daemon
2022-07-15 9:35 ` bugzilla-daemon
2022-07-15 9:37 ` bugzilla-daemon
2022-07-15 10:36 ` bugzilla-daemon
2022-07-15 10:43 ` bugzilla-daemon
2022-07-15 10:52 ` bugzilla-daemon
2022-07-15 11:00 ` bugzilla-daemon
2022-07-15 15:20 ` bugzilla-daemon
2022-07-15 15:20 ` bugzilla-daemon
2022-07-15 17:30 ` bugzilla-daemon
2022-07-15 17:32 ` bugzilla-daemon
2022-07-17 13:55 ` bugzilla-daemon
2022-07-17 13:57 ` bugzilla-daemon
2022-07-17 14:06 ` bugzilla-daemon
2022-07-17 17:53 ` bugzilla-daemon
2022-07-17 21:13 ` 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-216248-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.