Bug 198929 - Interrupt storm after suspend causes one busy kworker
Summary: Interrupt storm after suspend causes one busy kworker
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: EC (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: acpi_ec
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-25 12:14 UTC by Paul Menzel
Modified: 2018-05-30 06:09 UTC (History)
6 users (show)

See Also:
Kernel Version: 4.16-rc1
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Paul Menzel 2018-02-25 12:14:37 UTC
On the laptop TUXEDO Book 1406 since Linux 4.16-rc1, sometimes after resume from ACPI S3, the fan starts spinning really loud. Looking with `top`, one kworker thread(?) uses one CPU fully.

Checking with `$ grep -R . /sys/firmware/acpi/interrupts/`, the interrupts seem to three lines have really high values. (I accidentally overrode my file with the high values in it.)

1. /sys/firmware/acpi/interrupts/gpe66:      19  EN     enabled      unmasked
2. /sys/firmware/acpi/interrupts/sci:     126
3. /sys/firmware/acpi/interrupts/gpe50:     104  EN     enabled      unmasked
4. /sys/firmware/acpi/interrupts/gpe_all:     126

Do you know of changes in Linux 4.16-rc1, which could cause this?
Comment 1 Thorsten Leemhuis 2018-02-26 09:32:40 UTC
JFYI: This issues is tracked in the regression reports for Linux 4.16 (http://bit.ly/lnxregrep416 ) with this id:

Linux-Regression-ID: lr#41c451

Please include this line in the comment section of patches that are supposed to fix the issue. Please also mention the string once in other mailinglist threads or different bug tracking entries if you or someone else start to discuss the issue there. By including that string you make it a whole lot easier to track where an issue gets discussed and how far patches to fix it have made it. For more details on this please see here: http://bit.ly/lnxregtrackid

Thx for your help. Ciao, Thorsten
Comment 2 Chen Yu 2018-03-06 17:40:29 UTC
might need to check acpidump table to figure out what gpe50 and 66 are.
Comment 3 Chen Yu 2018-03-12 01:27:15 UTC
ping.
Comment 4 Zhang Rui 2018-05-02 03:51:29 UTC
@paul, do you still have the machine? if yes, please attach the acpidump.
Comment 5 Zhang Rui 2018-05-30 06:09:22 UTC
Bug closed as there is no response from Paul.
please feel free to reopen it if you can provide the information needed.

Note You need to log in before you can comment on or make changes to this bug.