Created attachment 280827 [details]
dmesg | grep Error

I have similar problems with ACPI. I'm using openSUSE 15.1 Leap Alpha. And also I installed 'kernel-default-4.20.5-1.1.g34ae151.nosrc' from https://download.opensuse.org/repositories/Kernel:/stable/standard/ .But I still have giving same problems. 

Here it is my bug report on https://bugzilla.opensuse.org/show_bug.cgi?id=1123248

This is a real problem? Because, when I use my computer, I don't feel anything about with this problem. But I wonder and want to find out why. Why are there these messages on every booting? What's the problem?

For me this part of a larger issue.  The buffer overflow is a weakness somebody could exploit.  Plus it seems not all of my hardware is being properly detected.  The problem is it might seem that HP is also making WMI calls and my report of this issue on Fedoras site and here have gone largely unanswered

These errors occur from a bytecode interpreter inside linux kernel called the Acpi machine language (AML) interpreter. The AML interpreter is being called from the OS (linux device drivers or driver frameworks) in order to enumerate and configure devices. Please upload the ACPI dump (acpidump.out) using the instructions on this website:

https://01.org/linux-acpi/utilities

Created attachment 281821 [details]
my acpidump output

I updated now.

Greetings,

This ticket took so long to be answered I removed Linux from the device.  I will re-install over the weekend and post up my findings on Monday.

Created attachment 281879 [details]
ACPI_dump

Linux was reloaded and here is the dump you requested.

Any updates?  I'm on kernel 4.20.16.200 and the issue still remains.  I still have yet another issue to get resolved before I can install graphics drivers.

Sorry about the late response. I'll take a look at this next week!

Any updates.  Anything I can do the help out?

Sorry about the absence.

Here's more information:

1.) _DSM warning:

[    2.184602] ACPI Warning: \_SB.PCI0.RP01.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20180810/nsarguments-66)

If you do not get ACPI errors several lines after this warning, this warning is not an issue. Just the AML interpreter complaining that the OS queried the interpreter with parameters that do not have the same type as specified in the ACPI specification.

2.) _CRT error

[    1.059909] ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x000000005) is beyond end of object (length 0x5) (20180810/exoparg2-396)
[    1.059915] ACPI Error: Method parse/execution failed \_TZ.GETP, AE_AML_PACKAGE_LIMIT (20180810/psparse-516)
[    1.059919] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, AE_AML_PACKAGE_LIMIT (20180810/psparse-516)
[    1.060845] ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x000000005) is beyond end of object (length 0x5) (20180810/exoparg2-396)
[    1.060850] ACPI Error: Method parse/execution failed \_TZ.GETP, AE_AML_PACKAGE_LIMIT (20180810/psparse-516)
[    1.060853] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, AE_AML_PACKAGE_LIMIT (20180810/psparse-516)
[    1.060858] [Firmware Bug]: No valid trip found

This is an interpreter error where TRIP is being accessed out of bounds. TRIP is a package (basically a tuple) containing thermal trip points.

Method (GETP, 2, Serialized)
{
    Local0 = Arg1
    If ((Arg1 == One))
    {
        Local3 = DerefOf (CUZO [Arg0])
        If (((Local3 > One) && (Local3 != 0xFF)))
        {
             Local0 = Zero
        }
    }

    Local2 = DerefOf (DerefOf (TRIP [Arg0]) [Local0])
    Return (Local2)
}

This is a firmware bug and I suggest contacting your laptop's manufacturer..

I'm still looking into the CAP1 error. This is one that can potentially be solved in the kernel.

Also, please provide the name of the system. Thanks

Also, please post the dmesg of this machine

Sorry, thought i added it.  Let me grab it from Fedoras bugzilla

Here link with the specs,  i have the model with 512 gb harddrive and 16 gigs of ram.  Same proc and monitor.

https://m.newegg.com/products/9SIA24G6R28560

Hi, @Erik, any update?

ping Erik. :p

@Sean, please provide the dmesg output requested in comment #11,
plus, the URL does not provide any useful information, please check the model name of your machine, or attach the dmidecode output.

I'm also affected. Using MX Linux MX-19.3
Notebook HP ProBook 440 G4 


dmidecode here: https://pastebin.com/PhXHjDng

Bug closed as there is no response from the bug reporter.
Please feel free to re-open it if the problem still exists in the latest upstream kernel.

Daniel, please file a new bug report.

(In reply to Zhang Rui from comment #18)
> Bug closed as there is no response from the bug reporter.
> Please feel free to re-open it if the problem still exists in the latest
> upstream kernel.
> 
> Daniel, please file a new bug report.

Thanks, Zhang. Will do.

(In reply to Zhang Rui from comment #18)
> Bug closed as there is no response from the bug reporter.
> Please feel free to re-open it if the problem still exists in the latest
> upstream kernel.
> 
> Daniel, please file a new bug report.

Thanks, Zhang. Will do.