Bug 199983

please attach the acpidump output

Created attachment 276489 [details]
The acpidump output.

so it is this piece of code that causes the failure
        Method (_PDC, 1, NotSerialized)  // _PDC: Processor Driver Capabilities
        {
            If (CondRefOf (\_PR.CPU0._PPC))
            {
                \_PR.CPU0._PPC () = CPPC /* \_PR_.CPPC */
            }

            Local0 = CPDC (Arg0)
            GCAP (Local0)
            Return (Local0)
        }


\_PR.CPU0._PPC is a method, and I don't understand how this piece of code is supposed to work.

@erik, can you please check if this is buggy ASL?

(In reply to Frank from comment #0)
> Since many kernel version's an error is logged on every boot.
> But the system looks running fine.
> 
> message:
> ACPI Error: Needed type [Reference], found [Integer]         (ptrval)
> (20180313/exresop-69)
> ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName
> unavailable] (20180313/dswexec-427)

OpcodeName unavailable seems a bit scary. Could you try upgrading to kernel version 4.18-rc1 or newer and check if you still have the same error in the dmesg?

Hi Erik,
on 4.18-rc1
I get the same message but only with other numbers:
ACPI Error: Needed type [Reference], found [Integer] (____ptrval____) (20180531/exresop-69)
ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20180531/dswexec-427)
ACPI Error: Method parse/execution failed \_PR.CPU0._PDC, AE_AML_OPERAND_TYPE (20180531/psparse-516)

hi, This is a firmware issue. If there aren't any symptoms that you experience because of this message, it's probably not a serious error. If you would like to try getting this error, you can try contacting the firmware vendor. I'll close this because this is a firmware issue rather than a linux kernel issue.

Are you 100% sure that this is a firmware bug ? If it's the case I will try to reach Lenovo to ask them to fix it (I suggest to anyone impacted to do it too). Thanks.

(In reply to paviluf from comment #7)
> Are you 100% sure that this is a firmware bug ? If it's the case I will try
> to reach Lenovo to ask them to fix it (I suggest to anyone impacted to do it
> too). Thanks.

Yes, what's happening is that there is an attempt to store an integer to a reference type in the bytecode.

(In reply to paviluf from comment #7)
> Are you 100% sure that this is a firmware bug ? If it's the case I will try
> to reach Lenovo to ask them to fix it (I suggest to anyone impacted to do it
> too). Thanks.

Similar bug: http://bugs.debian.org/1026965 , http://github.com/fwupd/firmware-lenovo/issues/119#issuecomment-1664825807 .   There, you have


Aug 04 00:34:14 MyPC kernel: ACPI Error: Needed [Integer/String/Buffer], found [Package] 000000007577f2c1 (20220331/exresop-469)
Aug 04 00:34:14 MyPC kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20220331/dswexec-431)
Aug 04 00:34:14 MyPC kernel: ACPI Error: Aborting method \ADBG due to previous error (AE_AML_OPERAND_TYPE) (20220331/psparse-529)
Aug 04 00:34:14 MyPC kernel: ACPI Error: Aborting method \_SB.HIDD._DSM due to previous error (AE_AML_OPERAND_TYPE) (20220331/psparse-529)
Aug 04 00:34:14 MyPC kernel: ACPI: \_SB_.HIDD: failed to evaluate _DSM b356ecee-4244-8f40-a792-4edd4d758054 (0x3003)


Similar but not exactly the same.  If you have not yet reached out to Lenovo, please do.