Hi Kernel Team, I noticed this messages at boot. Maybe someone has seen them before. You may know where these messages come from. [ 1.964245] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000044F (\GPIS) (20200925/utaddress-204) [ 1.964254] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20200925/utaddress-204) [ 1.964260] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 1.964264] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20200925/utaddress-204) [ 1.964269] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20200925/utaddress-204) [ 1.964274] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 1.964275] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20200925/utaddress-204) [ 1.964280] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20200925/utaddress-204) [ 1.964285] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 1.964286] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20200925/utaddress-204) [ 1.964291] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20200925/utaddress-204) [ 1.964296] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 1.966234] ACPI: bus type USB registered [ 2.119115] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x000000003) is beyond end of object (length 0x0) (20200925/exoparg2-393) [ 2.119121] ACPI Error: Aborting method \_SB.PCI0.GFX0._DSM due to previous error (AE_AML_PACKAGE_LIMIT) (20200925/psparse-529) [ 2.119131] ACPI: \_SB_.PCI0.GFX0: failed to evaluate _DSM (0x300b) [ 2.119135] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20200925/nsarguments-61) [ 2.119313] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x000000003) is beyond end of object (length 0x0) (20200925/exoparg2-393) [ 2.119317] ACPI Error: Aborting method \_SB.PCI0.GFX0._DSM due to previous error (AE_AML_PACKAGE_LIMIT) (20200925/psparse-529) [ 2.119323] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP._DSM due to previous error (AE_AML_PACKAGE_LIMIT) (20200925/psparse-529) [ 2.119329] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM (0x300b) [ 2.119331] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20200925/nsarguments-61) Debian 10 OS Laptop System: ASUSTeK product: X550VL v: 1.0 Linux laptop1-asus 5.10.25 #1 SMP Sat Mar 27 16:40:59 UTC 2021 x86_64 GNU/Linux
Created attachment 296207 [details] acpi.tar.bz
Created attachment 296209 [details] ACPI.txt
Created attachment 296211 [details] acpidump.txt
Created attachment 296213 [details] dmesg.txt
Created attachment 296215 [details] dmidecode.txt
Created attachment 296217 [details] inxi.txt
Created attachment 296219 [details] lspci.txt
Created attachment 296221 [details] uname.txt
From what I can see, all of these are caused by the bogus AML code of the ACIP BIOS, and there is nothing we can do in Linux kernel. If there is any real ACPI related functionality issue, please feel free to give more updates, or else, I'd prefer this bug closed because we cannot workaround this kind of issues in Linux kernel.