Bug 1461511
| Summary: | kworker/0:1 process load CPU up to 25% | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | ilya <ivmazurenko> | ||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 31 | CC: | galen.lynch, gansalmon, ichavero, itamar, ivmazurenko, jforbes, jonathan, kernel-maint, madhu.chinakonda, mchehab, niki.guldbrand, solovyov.s.n, svcrdhtbgzll | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-11-24 16:55:47 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
ilya
2017-06-14 16:06:10 UTC
sudo echo "disable" > /sys/firmware/acpi/interrupts/gpe03 - helps for me i have installed new ssd drive instead of dvdrom of my notebook. after that bug annoing me please help. bug reproduced in rhel, f25, f26 beta Any updates? I am seeing the same issue, and disabling one of the interrupts seems to work around this issue like this below, before doing this one of the CPU's was running at 100%: # echo "disable" > /sys/firmware/acpi/interrupts/gpe61 # cat /sys/firmware/acpi/interrupts/gpe61 3885813 STS disabled unmasked Don't know what relevant information I can provide to help debug this ? The hardware is a Laptop, running F27, I an seeing this in kernel 4.13.1[1,2,3] so far. We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs. Fedora 26 has now been rebased to 4.15.4-200.fc26. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27. If you experience different issues, please open a new bug report for those. The work around mentioned in this bug report (Disabling interrupts) worked for me, but haven't needed the work around for some time now. still reproduced. This bug is very annoying, please help. What additional information can i provide? I am also seeing this behaviour on my Dell XPS 9560 laptop $ uname -r && cat /etc/*release 4.18.11-200.fc28.x86_64 Fedora release 28 (Twenty Eight) NAME=Fedora VERSION="28 (Workstation Edition)" ID=fedora VERSION_ID=28 PLATFORM_ID="platform:f28" PRETTY_NAME="Fedora 28 (Workstation Edition)" ANSI_COLOR="0;34" CPE_NAME="cpe:/o:fedoraproject:fedora:28" HOME_URL="https://fedoraproject.org/" SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Fedora" REDHAT_BUGZILLA_PRODUCT_VERSION=28 REDHAT_SUPPORT_PRODUCT="Fedora" REDHAT_SUPPORT_PRODUCT_VERSION=28 PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy" VARIANT="Workstation Edition" VARIANT_ID=workstation Fedora release 28 (Twenty Eight) Fedora release 28 (Twenty Eight) $ grep . -r /sys/firmware/acpi/interrupts /sys/firmware/acpi/interrupts/gpe2F: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe23: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe5D: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe51: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe1F: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe13: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe4D: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe41: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe7B: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe0F: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe03: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe3D: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe31: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe6B: 0 STS invalid unmasked /sys/firmware/acpi/interrupts/gpe2D: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe21: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe5B: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe1D: 0 invalid unmasked /sys/firmware/acpi/interrupts/ff_pwr_btn: 0 EN enabled unmasked /sys/firmware/acpi/interrupts/gpe78: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe11: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe4B: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe0D: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe68: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe01: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe3B: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe58: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe2B: 0 invalid unmasked /sys/firmware/acpi/interrupts/ff_rt_clk: 0 disabled unmasked /sys/firmware/acpi/interrupts/ff_pmtimer: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe48: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe1B: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe76: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe38: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe0B: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe66: 7 EN enabled unmasked /sys/firmware/acpi/interrupts/gpe28: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe56: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe18: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe46: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe74: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe08: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe36: 0 STS invalid unmasked /sys/firmware/acpi/interrupts/gpe64: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe26: 0 invalid unmasked /sys/firmware/acpi/interrupts/error: 0 /sys/firmware/acpi/interrupts/gpe54: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe16: 0 invalid unmasked /sys/firmware/acpi/interrupts/sci: 9981 /sys/firmware/acpi/interrupts/gpe44: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe7E: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe72: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe06: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe34: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe6E: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe62: 0 EN enabled unmasked /sys/firmware/acpi/interrupts/gpe24: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe5E: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe52: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe14: 9963 EN enabled unmasked /sys/firmware/acpi/interrupts/gpe4E: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe42: 10 EN enabled unmasked /sys/firmware/acpi/interrupts/gpe7C: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe70: 0 STS invalid unmasked /sys/firmware/acpi/interrupts/gpe04: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe3E: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe32: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe6C: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe60: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe2E: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe22: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe5C: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe50: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe1E: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe79: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe12: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe4C: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe40: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe7A: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe0E: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe69: 0 disabled unmasked /sys/firmware/acpi/interrupts/gpe02: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe3C: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe30: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe6A: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe59: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe2C: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe20: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe5A: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe49: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe1C: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe77: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe10: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe4A: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe39: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe0C: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe67: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe00: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe3A: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe_all: 9984 /sys/firmware/acpi/interrupts/gpe29: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe57: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe2A: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe19: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe47: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe1A: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe75: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe09: 0 EN enabled unmasked /sys/firmware/acpi/interrupts/gpe37: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe0A: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe65: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe27: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe55: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe17: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe45: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe7F: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe73: 0 invalid unmasked /sys/firmware/acpi/interrupts/ff_gbl_lock: 0 disabled unmasked /sys/firmware/acpi/interrupts/gpe07: 0 invalid unmasked /sys/firmware/acpi/interrupts/sci_not: 17 /sys/firmware/acpi/interrupts/gpe35: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe6F: 1 EN enabled unmasked /sys/firmware/acpi/interrupts/gpe63: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe25: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe5F: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe53: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe15: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe4F: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe43: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe7D: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe71: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe05: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe3F: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe33: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe6D: 0 disabled unmasked /sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe61: 3 EN enabled unmasked Output of perf tracing suggests that the problem has to do with my usb-hub: $ sudo perf record -g -a sleep 10 $ sudo perf report ---The tree with the largest self time:--- - 56.04% 55.78% kworker/2:0+pm [kernel.kallsyms] [k] xhci_hub_control ▒ 55.78% ret_from_fork ▒ kthread ▒ worker_thread ▒ process_one_work ▒ pm_runtime_work ▒ rpm_idle ▒ __rpm_callback ▒ usb_runtime_idle ▒ __pm_runtime_suspend ▒ rpm_suspend ▒ rpm_callback ▒ __rpm_callback ▒ usb_runtime_suspend ▒ - usb_suspend_both ▒ - 47.34% hub_suspend ▒ set_port_feature ▒ usb_control_msg ▒ usb_start_wait_urb ▒ - usb_hcd_submit_urb ▒ xhci_hub_control ▒ - 8.43% usb_resume_interface.isra.9 ▒ hub_resume ▒ hub_activate ▒ hub_ext_port_status ▒ usb_control_msg ▒ usb_start_wait_urb ▒ - usb_hcd_submit_urb ▒ xhci_hub_control still reproduced What information can i Provide to help in fix of this bug? It is very annoying We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora 29 has now been rebased to 4.19.5-300.fc29. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. still reproduced Created attachment 1511191 [details]
lsmod output
lsmod output kernel 4.19.5-300.fc29.x86_64
Created attachment 1511192 [details]
dmesg
Same issue here on kernel 4.19.14-200.fc28. In my case it is the gpe2A interrupt that causes this issue and disabling it, works as workaround. I'm on a HP laptop zbook14. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora 29 has now been rebased to 4.20.5-200.fc29. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. This is still happening on Fedora 28, with an updated kernel. $ uname -r 4.20.6-100.fc28.x86_64 *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora 29 has now been rebased to 5.2.9-100.fc29. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 30, and are still experiencing this issue, please change the version to Fedora 30. If you experience different issues, please open a new bug report for those. I no longer have the laptop where I previously had the issue. On a fully updated Fedora 30, I'm not seeing this high cpu usage on a Dell E6230. Thanks for the reply. Still reproduced on Fedora 31. I have created this issue 2 years ago. Every time after installing of a fedora i need to make new systemd unit, thats makes the "sudo echo "disable" > /sys/firmware/acpi/interrupts/gpe03" command. Or my notebook becomes very hot and slow. Please, tell me, what data can I provide to make you able to fix this bug?? This is very annoying, please, stop ignoring this issue Also, reproduced in RHEL This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |