https://bugzilla.kernel.org/show_bug.cgi?id=196447

Zhang Rui ([email protected]) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |CLOSED
                 CC|                            |[email protected]
         Resolution|---                         |WILL_NOT_FIX

--- Comment #3 from Zhang Rui ([email protected]) ---
        Method (_L0B, 0, NotSerialized)  // _Lxx: Level-Triggered GPE
        {
            If (GPFG && \_SB.PCI0.LPC.NFCI)
            {
                GPFG = 0x00
                Notify (\_SB.PCI0.SMBU.NFC, 0xC0) // Hardware-Specific
            }
        }

                Device (NFC)
                {
                    Name (_HID, EisaId ("BCM2F21"))  // _HID: Hardware ID
                    Name (_CID, EisaId ("BCM2F21"))  // _CID: Compatible ID
                    Name (_UID, 0x00)  // _UID: Unique ID
                    ...
                }

According to google result, BCM2F21 sounds like a NFC SMBus device,
and we don't have the device support in Linux.

So I think this is an interrupt storm issue that the NFC event is triggered for
unknown reason, and then it keeps on firing as it is not handled in Linux
kernel.
please use boot option acpi_mask_gpe=0x0b as the workaround for this issue.
please feel free to reopen it if the high cpu usage issue still exists with the
boot option.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
acpi-bugzilla mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to