morytox Posted January 7 Share Posted January 7 Dear Unraid Team, today i was working on my unraid applications and did an unraid update from 6.12.1 to 6.12.6. At some point i figured that one core was stuck at 100% utilization permanently. Even after restart before even starting the array, instantly 100% usage on one core. In HTOP i could not see anything unusual aside emhttpd doing things sporadically. But i cannot find the culprit of using one core constantly. it also drives me crazy since cpu cooler now is always turning on and off due to load and probably power consumption is also significantly increased I added the diagnostics output as attachment. The stuck core changes with every reboot to another, but than that core stays at 100% constantly. Hope someone could help. blackbox-diagnostics-20240107-1557.zip Quote Link to comment
JorgeB Posted January 8 Share Posted January 8 Do you see the same if you boot in safe mode? 1 Quote Link to comment
morytox Posted January 8 Author Share Posted January 8 Hi JorgeB, so i restarted in safe mode, still pegged core at 100% Array Stopped obviously no docker or vm running. Samba WSD disabled. Also out of ideas from web research. Quote Link to comment
Solution JorgeB Posted January 8 Solution Share Posted January 8 root 293 59.5 0.0 0 0 ? R 15:44 7:35 \_ [kworker/3:1+usb_hub_wq] See if this helps: https://forums.unraid.net/topic/129514-high-cpu-load-caused-by-kworker-and-ksoftirqd-usb-auto-suspend/?do=findComment&comment=1179867 1 Quote Link to comment
morytox Posted January 9 Author Share Posted January 9 (edited) Hi JorgeB, yes sorry forgot to mention: i found this one as well and did try it out as well. I edited /boot/syslinux/syslinux.cfg using the cli in popupbrowser window and appended it using vi to the bottom of the file. No change after reboot. btw: there is another user havig similar symptoms: (heimdall-one quoted you in a topic: One Core is always at 90-100%) Don't know if that's relevant. Edited January 9 by morytox Quote Link to comment
itimpi Posted January 9 Share Posted January 9 5 minutes ago, morytox said: i found this one as well and did try it out as well. I edited /boot/syslinux/syslinux.cfg using the cli in popupbrowser window and appended it using vi to the bottom of the file. No change after reboot. That was the wrong place to add it! It needs to be added to the end of one of the 'append' lines for the boot option you are using. 1 Quote Link to comment
morytox Posted January 9 Author Share Posted January 9 Do you have an example ? I am not really sure and cannot finde a specific example, probably as such:? label Unraid OS menu default kernel /bizimage append initrd=/bzroot, usbcore.autosuspend=-1 label Unraid OS GUI Mode kernel /bizimage append initrd=/bzroot, /bzroot-gui, usbcore.autosuspend=-1 Quote Link to comment
itimpi Posted January 9 Share Posted January 9 Nearly right - you need to omit the commas as the options are space separated. Normally easiest to do it via Main->Boot Device->Syslinux Configuration 1 Quote Link to comment
morytox Posted January 9 Author Share Posted January 9 Thanks a lot @JorgeB & @itimpi, that solved it! Last question: Does this setting now limit me doing something or disables some functionality? Quote Link to comment
JorgeB Posted January 9 Share Posted January 9 It should not cause any issues. 1 Quote Link to comment
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.