Comment # 18 on bug 1185513 from Anthony Agelastos

(In reply to Joey Lee from comment #15)
> The real strange thing is in Anthony's ACPI tables. ACPI tables of his
> machine has _CPC method in processor 0 in ssdt15:
> 
>     Scope (\_PR.PR00)
>     {   
>         Method (_CPC, 0, NotSerialized)  // _CPC: Continuous Performance
> Control               
>         {   
>             If ((\_PR.CFGD & 0x01000000))
>             {   
>                 Return (CPOC) /* External reference */
>             }
>             Else
>             {   
>                 Return (CPC2) /* External reference */
>             }
>         }
>     }
> 
> It looks no problem, then I used two version ACPICA to verify the execution
> of \_PR.PR01._CPC. I can _NOT_ reproduce AE_NOT_FOUND error. The execution
> of \_PR.PR01._CPC is success:
> 
> - execute \_PR.PR01._CPC
> Evaluating \_PR.PR01._CPC
> Evaluation of \_PR.PR01._CPC returned object 0x18d6a90, external buffer
> length 3A8              
>   [Package] Contains 21 Elements:
>     [Integer] = 0000000000000015
> ...
> 
> Both of two version ACPICA (version 20210105 for v5.12 kernel and version
> 20201113 for v5.11 kernel) are success. 
> 
> Hi Anthony, 
> 
> Could you please confirm that you still see the AE_NOT_FOUND parsing error
> on _CPC with v5.12 kernel? Could you please help to attach dmesg log on
> bugzilla? 
> 
> Thanks

Hello Joey:

I updated from openSUSE Tumbleweed 20210427-0 -> 20210502-0 where the former
had 5.11 (5.11.16-1-default) and the new one 5.12 (5.12.0-2-default). The
errors persist. I attached a tarball that contains acpidump and dmesg info from
when I was in 5.11 and 5.12 to be compared. This was a fresh acpidump on 5.11
in case that helps. Thank you for your help with this ticket; your responses
are very much appreciated.