This bug was fixed in the package linux-oem-6.1 - 6.1.0-1017.17
---------------
linux-oem-6.1 (6.1.0-1017.17) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1017.17 -proposed tracker (LP: #2026459)
* Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
* CVE-2023-3269
- exec: Remove FOLL_FORCE for stack setup
- mm: introduce new 'lock_mm_and_find_vma()' page fault helper
- mm: make the page fault mmap locking killable
- arm64/mm: Convert to using lock_mm_and_find_vma()
- powerpc/mm: Convert to using lock_mm_and_find_vma()
- mips/mm: Convert to using lock_mm_and_find_vma()
- riscv/mm: Convert to using lock_mm_and_find_vma()
- arm/mm: Convert to using lock_mm_and_find_vma()
- mm/fault: convert remaining simple cases to lock_mm_and_find_vma()
- powerpc/mm: convert coprocessor fault to lock_mm_and_find_vma()
- mm: make find_extend_vma() fail if write lock not held
- execve: expand new process stack manually ahead of time
- mm: always expand the stack with the mmap write lock held
- [CONFIG]: Set CONFIG_LOCK_MM_AND_FIND_VMA
* CVE-2023-3389
- io_uring/poll: serialize poll linked timer start with poll removal
* amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged
(LP: #2025670)
- platform/x86/amd/pmf: Register notify handler only if SPS is enabled
* Mute/mic LEDs no function on some HP Platforms (LP: #2025444)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on
EliteBook
* Various backlight issues with the 6.0/6.1 kernel (LP: #2023638)
- ACPI: video: Stop trying to use vendor backlight control on laptops from
after ~2012
* HDMI output with More than one child device for port B in VBT error
(LP: #2025195)
- SAUCE: drm/i915/quirks: Add multiple VBT quirk for HP ZBook Power G10
-- You-Sheng Yang <[email protected]> Wed, 12 Jul 2023
11:26:03 +0800
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3269
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3389
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2025670
Title:
amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged
Status in linux package in Ubuntu:
New
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux source package in Lunar:
New
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
New
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2025670
[Impact]
Call trace dumped in events workqueue power_supply_changed_work, and
cpufreq locked to 400-544MHz.
```
[ 22.592162] Call Trace:
[ 22.592164] <TASK>
[ 22.592164] ? rcu_note_context_switch+0x5e0/0x660
[ 22.592166] ? __warn+0x81/0x130
[ 22.592171] ? rcu_note_context_switch+0x5e0/0x660
[ 22.592172] ? report_bug+0x171/0x1a0
[ 22.592175] ? prb_read_valid+0x1b/0x30
[ 22.592177] ? handle_bug+0x3c/0x80
[ 22.592178] ? exc_invalid_op+0x17/0x70
[ 22.592179] ? asm_exc_invalid_op+0x1a/0x20
[ 22.592182] ? rcu_note_context_switch+0x5e0/0x660
[ 22.592183] ? acpi_ut_delete_object_desc+0x86/0xb0
[ 22.592186] ? acpi_ut_update_ref_count.part.0+0x22d/0x930
[ 22.592187] __schedule+0xc0/0x1410
[ 22.592189] ? ktime_get+0x3c/0xa0
[ 22.592191] ? lapic_next_event+0x1d/0x30
[ 22.592193] ? hrtimer_start_range_ns+0x25b/0x350
[ 22.592196] schedule+0x5e/0xd0
[ 22.592197] schedule_hrtimeout_range_clock+0xbe/0x140
[ 22.592199] ? __pfx_hrtimer_wakeup+0x10/0x10
[ 22.592200] usleep_range_state+0x64/0x90
[ 22.592203] amd_pmf_send_cmd+0x106/0x2a0 [amd_pmf
bddfe0fe3712aaa99acce3d5487405c5213c6616]
[ 22.592207] amd_pmf_update_slider+0x56/0x1b0 [amd_pmf
bddfe0fe3712aaa99acce3d5487405c5213c6616]
[ 22.592210] amd_pmf_set_sps_power_limits+0x72/0x80 [amd_pmf
bddfe0fe3712aaa99acce3d5487405c5213c6616]
[ 22.592213] amd_pmf_pwr_src_notify_call+0x49/0x90 [amd_pmf
bddfe0fe3712aaa99acce3d5487405c5213c6616]
[ 22.592216] notifier_call_chain+0x5a/0xd0
[ 22.592218] atomic_notifier_call_chain+0x32/0x50
```
[Fix]
Upstream v6.4 fixed with commit
[146b6f6855e76](https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
drivers-x86.git/commit/?h=fixes&id=146b6f6855e7656e8329910606595220c761daac)
("platform/x86/amd/pmf: Register notify handler only if SPS is
enabled"). It has also been backported to stable trees v6.1.36
(oem-6.1 in v6.1.34 now), v6.2.15 (linux/lunar in v6.2.13 now),
v6.3.10 (linux/mantic in v6.3.8 now).
[Test Case]
1. boot with AC power cable connected
2. unplug power cable and check cpufreq
3. check no call trace found in dmesg
[Where problems could occur]
This patch installs only notify handler when the feature is fully
supported, so it's the right behavior.
[Other Info]
While we should receive this fix from stable fixes soon, nominate only
oem-6.1 to allow rolling out fix as soon as possible.
========== original bug description ==========
Upstream bugzilla https://bugzilla.kernel.org/show_bug.cgi?id=217571
This is specifically when a system advertises support for PMF, but
doesn't support static power slider for any reason.
Upstream fix in
https://github.com/torvalds/linux/commit/146b6f6855e7656e8329910606595220c761daac,
which has been backported to v6.1.36 (oem-6.1 in v6.1.34 now), v6.2.15
(linux/lunar in v6.2.13), v6.3.10 (linux/mantic in v6.3.8), v6.4.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025670/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
