Created attachment 209491 [details] acpidump My system doesn't boot normally with 4.5 kernel. It prints the message: ACPI Error: No handler or method for GPE N, disabling event (20160108/evgpe-790) continiously so that systemd journald eats 100% of one cpu core and dmesg is not readable. The "N" number after "GPE" loops continiously through these values: 00 01 05 10 13 14 15 16 17 The hardware is HP 4535s notebook with AMD A4 APU. Tried updating BIOS to the latest version - it didn't give any results. The distro is siduction (almost debian sid, I've tried both siduction(release) and debian(RC7) kernels - they behave equally). If I don't propagate the "quiet" param to the kernel - the log message stream will be so solid that the system won't boot at all. I'm able to boot without any problems if I propagate acpi=off, but then ACPI features, such as CPU frequency scaling, don't work of course. The 4.2.3 kernel is working nicely in my case. acpidump output is completely equal in 4.5 and 4.2.3 - I've attached it.
I am also affected by this error. Upgrading from 4.4.x to 4.5. Screenshot of the Kernel Log in rescue mode under systemd: https://drive.google.com/file/d/0B3pmY9R_R3jqamJ6d2owMmpZQ2M/view Distribution: Gentoo Linux Kernel: =sys-kernel/vanilla-sources-4.5.0 GCC: 4.9.3 glibc: 2.21
additional information: System: ThinkPad Edge E545 http://support.lenovo.com/ch/de/products/laptops-and-netbooks/thinkpad-edge-laptops/thinkpad-edge-e545/20b2/000kmz Firmware: BIOS/UEFI 1.13 (HRET25WW) ECP 1.13 (HRHT25WW) 2015/08/12
I also run into this with 4.5 kernel. Distribution: Arch Linux with linux-4.5. CPU: AMD A4-5000 APU with Radeon(TM) HD 8330 Graphics Laptop Model: ThinkPad Edge E145 BIOS Version: HSET56WW (2.01 ), 11/20/2013 Journal with said ACPI Errors at the bottom: http://pastebin.com/raw/pRuVpEhL acpidump: http://pastebin.com/raw/xTcm7yuj
Created attachment 210451 [details] systemd journal
Created attachment 210461 [details] acpidump Lenovo E145
Did this work in a kernel before 4.5? If yes, what is the latest kernel that works? Can you bit bisect to see what caused this failure?
Created attachment 211181 [details] lspci -vvnn on Lenovo Edge E145 On Arch Linux stable kernel version 4.4.5 the bug does not occur, on all versions above 4.5-rc1 i get the buggy behaviour. I did a git bisect from tag v4.4 to tag v4.5-rc1. The resulting first bad commit is bdecfcd : > commit bdecfcdb5461834aab24002bb18d3cbdd907b7fb > Author: Huang Rui <ray.huang@amd.com> > Date: Mon Nov 23 18:07:35 2015 +0800 > > sp5100_tco: fix the device check for SB800 and later chipsets > > For SB800 and later chipsets, the register definitions are the same > with SB800. And for SB700 and older chipsets, the definitions should > be same with SP5100/SB7x0. By its very nature, the parent of this commit does not cause the bug. The attached lspci output of my machine shows that i have a chipset that is covered by the module sp5100_tco. In fact, on 4.5 kernels this module gets loaded, while on 4.4.5 it does not. On 4.4.5 kernel: > $> uname -a > Linux godot 4.4.5-1-custom #1 SMP PREEMPT Tue Mar 22 00:15:20 CET 2016 x86_64 > GNU/Linux > $> sudo lspci -vvnn |grep '4385\|780b\|790b\|sp5100' 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:780b] (rev 3a) > $> lsmod | grep sp5100 > (empty) > $> grep sp5100 /lib/modules/4.4.5-1-custom/modules.dep > kernel/drivers/watchdog/sp5100_tco.ko.gz: On 4.5 kernel: > $> uname -a > Linux godot 4.5.0-1-custom45 #1 SMP PREEMPT Wed Mar 23 10:31:35 CET 2016 > x86_64 GNU/Linux > $> sudo lspci -vvnn |grep '4385\|780b\|790b\|sp5100' > 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller > [1022:780b] (rev 3a) > Kernel modules: i2c_piix4, sp5100_tco > $> lsmod |grep sp5100 > sp5100_tco 16384 0 On "shutdown +0" the module even prints an error shortly before the system halts, something like > sp5100_tcp: Unexpected close, not stopping watchdog!
Same results are debugged out from another bug (bug 114201). Please refer to it.
My APU is AMD A4 3300M, if it matters.
Please report this bug to bug 114201. Let me mark it as duplicate and close. *** This bug has been marked as a duplicate of bug 114201 ***
Closing, please track it in 114201.