Bug 1609192 - Lenovo T460p - ACPI BIOS Error (bug): PR.CPU0._PCC, AE_ALREADY_EXIST and PR.CPU0._CPC, AE_NOT_FOUND
Summary: Lenovo T460p - ACPI BIOS Error (bug): PR.CPU0._PCC, AE_ALREADY_EXIST and PR.C...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 28
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: 2018-07-27 09:10 UTC by Aurel
Modified: 2019-05-28 19:24 UTC (History)
22 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 19:24:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
ACPI Bios errors (27.80 KB, image/jpeg)
2018-07-27 09:10 UTC, Aurel
no flags Details
acpidump output on 4.18.13 (195.39 KB, application/zip)
2018-10-25 14:38 UTC, madstitz
no flags Details

Description Aurel 2018-07-27 09:10:58 UTC
Created attachment 1471026 [details]
ACPI Bios errors

Description of problem:
After a fresh install of Fedora 28, at boot time a list of ACPI errors show up (see the screenshot attached for complete list).

ACPI BIOS Error (bug): Failure creating [_PR.CPU0._PCC], AE_ALREADY_EXISTS (20180313/dswload2-316)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (201803/psobject-221)
ACPI Error: Ignore error and continue table load (20180313/psobject-604)
ACPI BIOS Error (bug): Could not resolve [_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180313/psargs-330)
ACPI Error: Method parse/execution failed _PR.CPU0._CPC, AE_NOT_FOUND (20180313/psparse-516)

It repeats for different number of CPU (CPU0, CPU1, etc)

Version-Release number of selected component (if applicable):
After system updates:
4.17.7-200.fc28.x86_64 #1 SMP Tue Jul 17 16:28:31 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


How reproducible:
At each boot before unlocking encrypted disk.

Steps to Reproduce:
1. just boot Fedora

Actual results:
The listed errors

Expected results:
No errors

Additional info:
Laptop : Lenovo T460p. Full disk encryption.

Comment 1 Laura Abbott 2018-10-01 21:20:42 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.
 
Fedora 28 has now been rebased to 4.18.10-300.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.
 
If you experience different issues, please open a new bug report for those.

Comment 2 Gurenko Alex 2018-10-02 07:17:20 UTC
(In reply to Laura Abbott from comment #1)
> We apologize for the inconvenience.  There is a large number of bugs to go
> through and several of them have gone stale.  Due to this, we are doing a
> mass bug update across all of the Fedora 28 kernel bugs.
>  
> Fedora 28 has now been rebased to 4.18.10-300.fc28.  Please test this kernel
> update (or newer) and let us know if you issue has been resolved or if it is
> still present with the newer kernel.
>  
> If you have moved on to Fedora 29, and are still experiencing this issue,
> please change the version to Fedora 29.
>  
> If you experience different issues, please open a new bug report for those.

Just updated this morning to 4.18.10 and the problem still exists, getting following in dmesg:

[    0.534229] ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180531/psargs-330)
[    0.534258] ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180531/psparse-516)
[    0.534348] ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180531/psargs-330)
[    0.534374] ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180531/psparse-516)
[    0.534398] ACPI Error: Method parse/execution failed \_PR.CPU1._CPC, AE_NOT_FOUND (20180531/psparse-516)
[    0.534470] ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180531/psargs-330)
[    0.534495] ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180531/psparse-516)
[    0.534519] ACPI Error: Method parse/execution failed \_PR.CPU2._CPC, AE_NOT_FOUND (20180531/psparse-516)
[    0.534588] ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180531/psargs-330)
[    0.534613] ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180531/psparse-516)
[    0.534637] ACPI Error: Method parse/execution failed \_PR.CPU3._CPC, AE_NOT_FOUND (20180531/psparse-516)
[    0.534704] ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180531/psargs-330)
[    0.534729] ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180531/psparse-516)
[    0.534758] ACPI Error: Method parse/execution failed \_PR.CPU4._CPC, AE_NOT_FOUND (20180531/psparse-516)
[    0.534822] ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180531/psargs-330)
[    0.534848] ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180531/psparse-516)
[    0.534871] ACPI Error: Method parse/execution failed \_PR.CPU5._CPC, AE_NOT_FOUND (20180531/psparse-516)
[    0.534938] ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180531/psargs-330)
[    0.534963] ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180531/psparse-516)
[    0.534987] ACPI Error: Method parse/execution failed \_PR.CPU6._CPC, AE_NOT_FOUND (20180531/psparse-516)
[    0.535070] ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180531/psargs-330)
[    0.535096] ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180531/psparse-516)
[    0.535119] ACPI Error: Method parse/execution failed \_PR.CPU7._CPC, AE_NOT_FOUND (20180531/psparse-516)

Comment 3 madstitz 2018-10-25 14:38:08 UTC
Created attachment 1497495 [details]
acpidump output on 4.18.13

output of: 
acpidump > acpidump
acpixtract acpidump

Comment 4 Petr Matyáš 2018-10-31 08:31:35 UTC
I had the same problem on T460p with kernel 4.18.16, this was preventing me from starting the OS (ArchLinux) when the notebook was docked and also prevented waking up from sleep when docked.

However I no longer have the kernel as I upgraded to LTS kernel 4.14.78 and everything is working on that one.

Comment 5 marcvw 2018-12-28 09:44:53 UTC
This bug still applies to F29 on my T460p with latest BIOS and updates installed. However I do not have found any issues so far, my system has been reinstalled yesterday.

 marc  ~  uname -a
Linux lenovo-t460p 4.19.10-300.fc29.x86_64 #1 SMP Mon Dec 17 15:34:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
 marc  ~  lsb_release 
LSB Version:	:core-4.1-amd64:core-4.1-noarch
 marc  ~  cat /etc/redhat-release 
Fedora release 29 (Twenty Nine)

BIOS Information
        Vendor: LENOVO
        Version: R07ET87W (2.27 )
        Release Date: 09/27/2018

System Information
        Manufacturer: LENOVO
        Product Name: 20FWCTO1WW
        Version: ThinkPad T460p

journalctl -p err;
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Failure creating [\_PR.CPU0._PPC], AE_ALREADY_EXISTS (20180810/dswload2-316)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-543)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Failure creating [\_PR.CPU0._PCT], AE_ALREADY_EXISTS (20180810/dswload2-316)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-543)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Failure creating [\_PR.CPU0._PSS], AE_ALREADY_EXISTS (20180810/dswload2-316)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-543)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Failure creating [\_PR.CPU0.LPSS], AE_ALREADY_EXISTS (20180810/dswload2-316)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Failure creating [\_PR.CPU0.TPSS], AE_ALREADY_EXISTS (20180810/dswload2-316)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Failure creating [\_PR.CPU0.PSDF], AE_ALREADY_EXISTS (20180810/dswload2-316)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Failure creating [\_PR.CPU0._PSD], AE_ALREADY_EXISTS (20180810/dswload2-316)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-543)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Failure creating [\_PR.CPU0.HPSD], AE_ALREADY_EXISTS (20180810/dswload2-316)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Failure creating [\_PR.CPU0.SPSD], AE_ALREADY_EXISTS (20180810/dswload2-316)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180810/psargs-330)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180810/psparse-516)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180810/psargs-330)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180810/psparse-516)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU1._CPC, AE_NOT_FOUND (20180810/psparse-516)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180810/psargs-330)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180810/psparse-516)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU2._CPC, AE_NOT_FOUND (20180810/psparse-516)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180810/psargs-330)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180810/psparse-516)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU3._CPC, AE_NOT_FOUND (20180810/psparse-516)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180810/psargs-330)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180810/psparse-516)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU4._CPC, AE_NOT_FOUND (20180810/psparse-516)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180810/psargs-330)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180810/psparse-516)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU5._CPC, AE_NOT_FOUND (20180810/psparse-516)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180810/psargs-330)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180810/psparse-516)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU6._CPC, AE_NOT_FOUND (20180810/psparse-516)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI BIOS Error (bug): Could not resolve [\_PR.CPU0._CPC.CPC1], AE_NOT_FOUND (20180810/psargs-330)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU0._CPC, AE_NOT_FOUND (20180810/psparse-516)
Dec 28 11:30:20 lenovo-t460p kernel: ACPI Error: Method parse/execution failed \_PR.CPU7._CPC, AE_NOT_FOUND (20180810/psparse-516)

Comment 6 Justin M. Forbes 2019-01-29 16:25:00 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.

Fedora 28 has now been rebased to 4.20.5-100.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.

If you experience different issues, please open a new bug report for those.

Comment 7 Gurenko Alex 2019-01-30 08:09:09 UTC
(In reply to Justin M. Forbes from comment #6)
> *********** MASS BUG UPDATE **************
> 
> We apologize for the inconvenience.  There are a large number of bugs to go
> through and several of them have gone stale.  Due to this, we are doing a
> mass bug update across all of the Fedora 28 kernel bugs.
> 
> Fedora 28 has now been rebased to 4.20.5-100.fc28.  Please test this kernel
> update (or newer) and let us know if you issue has been resolved or if it is
> still present with the newer kernel.
> 
> If you have moved on to Fedora 29, and are still experiencing this issue,
> please change the version to Fedora 29.
> 
> If you experience different issues, please open a new bug report for those.

The issue still exists on latest kernel (4.20.5-200.fc29.x86_64)

Comment 8 Ben Cotton 2019-05-02 19:57:22 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 Fedora 'version' of '28'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Gurenko Alex 2019-05-03 09:28:17 UTC
Issue still exists on F30 with kernel 5.0.10-300.fc30.x86_64. Can we bump the version in the BZ?

Comment 10 Ben Cotton 2019-05-28 19:24:20 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.