This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy' to 'verification-
done-jammy'. If the problem
This bug is awaiting verification that the linux-aws/5.15.0-1034.38
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.15.0-1036.43
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
Verify passed by checking the linux/5.15.0-68.75 kernel in -proposed
dmesg,
The "[\_SB.PR00._CPC], AE_NOT_FOUND" is gone and the dinamic ssdt
table(such as ApHwp etc.) are loaded.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug
I have tried kernel 5.15.0-68.75 in jammy on a Precision 5720 AIO and I
no longer see messages that it "Could not resolve symbol
[\_PR.CPU*._CPC]". In that sense, this fix partially addresses
https://bugzilla.kernel.org/show_bug.cgi?id=213023. However, acpi_cppc
support still appears to be absent
This bug is awaiting verification that the linux/5.15.0-68.75 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change
This set is part of v5.19 upstream.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Ivan Hu (ivan.hu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2006077
Title:
Fix the ACPI _CPC not found error from kernel dmesg on
** Summary changed:
- Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT
tables firmware
+ Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT
table loaded firmwares
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
--
13 matches
Mail list logo
