Bug 2075387 - ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND
Summary: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 35
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-14 04:49 UTC by Takehiko Abe
Modified: 2022-12-13 17:42 UTC (History)
19 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-12-13 17:42:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Linux Kernel 213023 0 P1 REOPENED Could not resolve symbol [\_PR.CPU0._CPC] 2022-06-29 21:03:05 UTC
Red Hat Bugzilla 1963717 1 unspecified CLOSED ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC] 2022-06-25 06:27:35 UTC

Description Takehiko Abe 2022-04-14 04:49:56 UTC
kernel-5.16.19-200.fc35.x86_64

5.16.19 brought back the bug: https://bugzilla.redhat.com/show_bug.cgi?id=1963717

The bug was previously fixed with the commit 159d8c274fd9:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=159d8c274fd9

but it was reverted with:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=8e5a2398e704

Comment 1 Ben Cotton 2022-11-29 18:45:10 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Ben Cotton 2022-12-13 17:42:38 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.