Description of problem: I have DELL 3530 laptop. I found that after some time of runtime (a few hours) my fan starts to turn fast and make noise. I checked what wrong and found that there is process irq/51-DELL0820 which tunes one core up to 100%, heats it and therefore fan speeds up. I'm pretty sure that when I installed FC28 in mid of summer, there was no such issue. I started to observe it a few weeks (4-6) ago. Therefore I expect it came with some new kernel release. Right now I use 4.18.17-200.fc28.x86_64 and tested vmlinuz-4.19.3-200.fc28.x86_64 with same result. With all 4.18.x releases I have in computer (4.18.13-17) I'm observing same issue. I updated BIOS to latest version (after I started to observing the issue), but no change. Version-Release number of selected component (if applicable): Kernel 4.18.x and 4.19.x How reproducible: Every day, a few ours after start or wakeup of laptop. Steps to Reproduce: 1. Start or wakeup the laptop 2. Wait till fan starts to turn fast (a few hours) 3. Top/ps of processes Actual results: top - 14:18:28 up 6 days, 17:50, 1 user, load average: 0.97, 1.00, 1.03 Tasks: 307 total, 1 running, 206 sleeping, 0 stopped, 2 zombie %Cpu(s): 5.1 us, 2.0 sy, 0.0 ni, 89.0 id, 0.0 wa, 3.7 hi, 0.2 si, 0.0 st KiB Mem : 16208868 total, 2552188 free, 1836624 used, 11820056 buff/cache KiB Swap: 33554428 total, 33551604 free, 2824 used. 13856852 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 703 root -51 0 0 0 0 D 6.2 0.0 19:47.46 irq/51-DELL0820 ... cat /proc/interrupts | grep 51: 51: 90419204 0 0 0 0 0 0 0 0 0 55333 0 IR-IO-APIC 51-fasteoi DELL0820:00 There is about 1-10k of new interrupts per second. Additional info: It looks it is related to DELL HW because 0820:00 is part of ID related to Mouse, Touchpad and one more UNKNOWN device: DELL0820:00 044E:121F Mouse DELL0820:00 044E:121F Touchpad DELL0820:00 044E:121F UNKNOWN but I don't know why older kernels were OK with it and new ones are receiving so much interrupts. I'm open to experiment to solve the issue. Best regards, Jirka Novak
*********** 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 28 kernel bugs. Fedora 28 has now been rebased to 4.20.5-100.fc28. 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 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
Hello, tested with 4.20.6-100.fc28.x86_64, no change. Best regards, Jirka Novak
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.