* seeing this error (not oops) on kernel logs

let me know if you need acpi dump, dmidecode or any other info.

Yeah you have provided very little here. We need a full kernel log, an acpidump and information about when this regressed.

Created attachment 307736 [details]
ACPI Dump

via `sudo acpidump > acpi_dump.txt`

Created attachment 307737 [details]
kernel full log hostname anonymized

via `journalctl --no-hostname --boot --no-pager > kernel_boot_log.txt`

Hi Mario,
Thank you for the reply. I attached full kernel log and an acpidump. I see this GPIO error during every boot. I remember I saw this error in older kernels as well, before upgrading to newer kernels.

Let me know if you need any further info.

Sincerely,
Atiq

This is a BIOS bug.  There are two devices that are declaring to use GPIO 0, but with different configuration.

Here is the first one:

>         Device (BTNS)
>         {
>             Name (_HID, "ACPI0011" /* Generic Buttons Device */)  // _HID:
>             Hardware ID
>             Name (_DDN, "Generic buttons device")  // _DDN: DOS Device Name
>             Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource
>             Settings
>             {
>                 Name (RBUF, ResourceTemplate ()
>                 {
>                     GpioInt (Edge, ActiveBoth, Exclusive, PullUp, 0x0000,
>                         "\\_SB.GPIO", 0x00, ResourceConsumer, ,
>                         )
>                         {   // Pin list
>                             0x0000
>                         }
>                 })
>                 Return (RBUF) /* \_SB_.BTNS._CRS.RBUF */
>             }

And here is the second one:

>     Scope (\_SB.GPIO)
>     {
>         Method (_AEI, 0, NotSerialized)  // _AEI: ACPI Event Interrupts
>         {
>             Name (BUF0, ResourceTemplate ()
>             {
>                 GpioInt (Edge, ActiveHigh, ExclusiveAndWake, PullDefault,
>                 0x1388,
>                     "\\_SB.GPIO", 0x00, ResourceConsumer, ,
>                     )
>                     {   // Pin list
>                         0x0000
>                     }

The kernel is behaving properly.  Please check for a BIOS update and report it to ASUS if it's happening on the latest BIOS.

Escalated this to Asus Support.

Case# N2503015169-0001

Asus Support said this,

> We regret to inform you that we are currently limited in the support we are
> able to provide for Linux operating systems. For the best possible software
> support, please contact the software manufacturer for further assistance.

I replied on their comment. Let's see if this moves forward!