https://bugzilla.kernel.org/show_bug.cgi?id=218531
Bug ID: 218531 Summary: Continuous ACPI errors resulting in high CPU usage by journald Product: ACPI Version: 2.5 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P3 Component: Other Assignee: acpi_ot...@kernel-bugs.osdl.org Reporter: danilrybakov...@gmail.com Regression: No Overview: After updating from lts v6.6.14-2 to lts v6.6.17-1 noticed high CPU temperature and lag. After running htop noticed that journald was using 30-60% of CPU. Afterwards, tried switching to stable, or lts v6.6.18-1, but encountered the same issue. Running journalctl -f gives these lines over and over again: Feb 19 21:09:12 danirybe kernel: ACPI Error: Could not disable RealTimeClock events (20230628/evxfevnt-243) Feb 19 21:09:12 danirybe kernel: ACPI Error: No handler or method for GPE 08, disabling event (20230628/evgpe-839) Feb 19 21:09:12 danirybe kernel: ACPI Error: No handler or method for GPE 0A, disabling event (20230628/evgpe-839) Feb 19 21:09:12 danirybe kernel: ACPI Error: No handler or method for GPE 0B, disabling event (20230628/evgpe-839) Feb 19 21:09:12 danirybe kernel: ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20230628/evevent-255) Feb 19 21:09:12 danirybe kernel: ACPI Error: No installed handler for fixed event - PowerButton (2), disabling (20230628/evevent-255) Feb 19 21:09:12 danirybe kernel: ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20230628/evevent-255) My system info: Laptop model: ASUS VivoBook D540NV-GQ065T OS: Arch Linux x86_64 Kernel: 6.6.14-2-lts WM: sway CPU: Intel Pentium N420 (4) @ 2.500GHz GPU1: Intel Apollo Lake [HD Graphics 505] GPU2: NVIDIA GeForce 920MX I've pinned down the commit after which the problem occurs: 847e1eb30e269a094da046c08273abe3f3361cf2 is the first bad commit commit 847e1eb30e269a094da046c08273abe3f3361cf2 Author: Shin'ichiro Kawasaki <shinichiro.kawas...@wdc.com> Date: Mon Jan 8 15:20:58 2024 +0900 platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe commit 5913320eb0b3ec88158cfcb0fa5e996bf4ef681b upstream. p2sb_bar() unhides P2SB device to get resources from the device. It guards the operation by locking pci_rescan_remove_lock so that parallel rescans do not find the P2SB device. However, this lock causes deadlock when PCI bus rescan is triggered by /sys/bus/pci/rescan. The rescan locks pci_rescan_remove_lock and probes PCI devices. When PCI devices call p2sb_bar() during probe, it locks pci_rescan_remove_lock again. Hence the deadlock. To avoid the deadlock, do not lock pci_rescan_remove_lock in p2sb_bar(). Instead, do the lock at fs_initcall. Introduce p2sb_cache_resources() for fs_initcall which gets and caches the P2SB resources. At p2sb_bar(), refer the cache and return to the caller. Before operating the device at P2SB DEVFN for resource cache, check that its device class is PCI_CLASS_MEMORY_OTHER 0x0580 that PCH specifications define. This avoids unexpected operation to other devices at the same DEVFN. Link: https://lore.kernel.org/linux-pci/6xb24fjmptxxn5js2fjrrddjae6twex5bjaftwqsuawuqqqydx@7cl3uik5ef6j/ Fixes: 9745fb07474f ("platform/x86/intel: Add Primary to Sideband (P2SB) bridge support") Cc: sta...@vger.kernel.org Suggested-by: Andy Shevchenko <andriy.shevche...@linux.intel.com> Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawas...@wdc.com> Link: https://lore.kernel.org/r/20240108062059.3583028-2-shinichiro.kawas...@wdc.com Reviewed-by: Andy Shevchenko <andriy.shevche...@linux.intel.com> Reviewed-by: Ilpo Järvinen <ilpo.jarvi...@linux.intel.com> Tested-by Klara Modin <klarasmo...@gmail.com> Reviewed-by: Hans de Goede <hdego...@redhat.com> Signed-off-by: Hans de Goede <hdego...@redhat.com> Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org> drivers/platform/x86/p2sb.c | 180 ++++++++++++++++++++++++++++++++++---------- 1 file changed, 139 insertions(+), 41 deletions(-) -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla