Tony325 Posted March 4, 2023 Share Posted March 4, 2023 hi everyone! I upgraded my UNRAID system from 6.10.3 to 6.11.5. I found that every 20 seconds a process would randomly make a CPU thread occupy 100%. Continued for 7, 8 seconds back to normal, and repeated after 20 seconds. The process name is kworker/ : +events. This situation does not exist in version 6.10.3. Finally, I hope someone can give me some suggestions or ways to deal with this situation. Thanks in advance to everyone who has gone to the trouble of helping others in the community. diagnostics-20230304-1829.zip Quote Link to comment
JorgeB Posted March 8, 2023 Share Posted March 8, 2023 Please reboot in safe mode, disable docker/VM services and check if you still have the same issue. Quote Link to comment
Tony325 Posted March 9, 2023 Author Share Posted March 9, 2023 20 hours ago, JorgeB said: Please reboot in safe mode, disable docker/VM services and check if you still have the same issue. I tested it, and the issue still exists in safe mode, even when The Array is not started. Quote Link to comment
JorgeB Posted March 9, 2023 Share Posted March 9, 2023 See if this helps: https://askubuntu.com/questions/176565/why-does-kworker-cpu-usage-get-so-high Quote Link to comment
lordsnoake Posted March 9, 2023 Share Posted March 9, 2023 i am actually experiencing the same error, except my kworker is kworker/4:1+pm I see the same thing, with or without safe mode, with or without the array started, and I have unplugged just about everything as well but no avail to me. The article that @JorgeB pointed out, i have looked at it as well but i am not sure if the results that come out of that are the problem or not, i.e Spoiler grep . -r /sys/firmware/acpi/interrupts/ /sys/firmware/acpi/interrupts/gpe1F: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe13: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe0F: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe03: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe1D: 0 disabled unmasked /sys/firmware/acpi/interrupts/ff_pwr_btn: 0 EN enabled unmasked /sys/firmware/acpi/interrupts/gpe11: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe0D: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe01: 0 invalid unmasked /sys/firmware/acpi/interrupts/ff_rt_clk: 0 STS disabled unmasked /sys/firmware/acpi/interrupts/ff_pmtimer: 0 STS invalid unmasked /sys/firmware/acpi/interrupts/gpe1B: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe0B: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe18: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe08: 0 EN enabled unmasked /sys/firmware/acpi/interrupts/error: 0 /sys/firmware/acpi/interrupts/gpe16: 0 invalid unmasked /sys/firmware/acpi/interrupts/sci: 0 /sys/firmware/acpi/interrupts/gpe06: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe14: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe04: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe1E: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe12: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe0E: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe02: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe1C: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe10: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe0C: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe00: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe_all: 0 /sys/firmware/acpi/interrupts/gpe19: 0 disabled unmasked /sys/firmware/acpi/interrupts/gpe1A: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe09: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe0A: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe17: 0 invalid unmasked /sys/firmware/acpi/interrupts/ff_gbl_lock: 0 EN enabled unmasked /sys/firmware/acpi/interrupts/gpe07: 0 invalid unmasked /sys/firmware/acpi/interrupts/sci_not: 0 /sys/firmware/acpi/interrupts/gpe15: 0 invalid unmasked /sys/firmware/acpi/interrupts/gpe05: 0 invalid unmasked /sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid unmasked Quote Link to comment
lordsnoake Posted March 16, 2023 Share Posted March 16, 2023 I figured my problem. Mine was that my motherboard started to fail 1 Quote Link to comment
.thumb.jpg.c54ccdc4cf8069fed8c125d805d1e3b7.jpg)
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.