Description of problem: journald is spamming like crazy. Today during a second 20:53:14 i got 1098 messages like that: [...] kwi 24 20:53:14 mamut2 kernel: ACPI Error: No handler or method for GPE 01, disabling event (20160108/evgpe-790) kwi 24 20:53:14 mamut2 systemd-journald[4982]: Missed 128 kernel messages kwi 24 20:53:14 mamut2 kernel: ACPI Error: No handler or method for GPE 0A, disabling event (20160108/evgpe-790) kwi 24 20:53:14 mamut2 systemd-journald[4982]: Missed 136 kernel messages kwi 24 20:53:14 mamut2 kernel: ACPI Error: No handler or method for GPE 07, disabling event (20160108/evgpe-790) kwi 24 20:53:14 mamut2 systemd-journald[4982]: Missed 110 kernel messages kwi 24 20:53:14 mamut2 kernel: ACPI Error: No handler or method for GPE 06, disabling event (20160108/evgpe-790) kwi 24 20:53:14 mamut2 systemd-journald[4982]: Missed 101 kernel messages kwi 24 20:53:14 mamut2 kernel: ACPI Error: No handler or method for GPE 01, disabling event (20160108/evgpe-790) [...] Sometimes it happens during installation from the live media. System on my laptop (only dual core 900MHz with integrated Radeon) is totally unusable. Journald takes almost 100% of CPU, even "sudo rebooot" doesn't respond and hang for 5 minutes. Version-Release number of selected component (if applicable): Whatever is on Fedora 24 right now. How reproducible: Not very often and I have no idea how to provoke that behaviour. Steps to Reproduce: 1. Run Fedora 24. 2. Wait... 3. Actual results: Journald is spamming thousand messages per second. Expected results: Journald isn't spamming thousand messages per second. I know that something is wrong, but doesn't have to be remindered every milisecond. :) Additional info: I'm really stuck. Please give me at least a clue to understand what is happening. I'm hoping that it can be fixed. Thanks.
This is a kernel issue, not acpid.
Reassigning to kernel per comment 1.
Looks like patch (at least for 4.6 kernel) is on the way: https://bugzilla.kernel.org/show_bug.cgi?id=114201#c44 For now, blacklisting module sp5100_tco in /etc/default/grub seems to help.
*** This bug has been marked as a duplicate of bug 1328633 ***
*** Bug 1335622 has been marked as a duplicate of this bug. ***