Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just today I find I have about 7 clusters of processes comprising groups of "cpuhp<digit>, migration/<digit>, ksoftirqd<digit>, kworker<digit>, kworker<digit>-kblockd" and I have no idea how to control this, which I suspect is totally useless behaviour just to use free cpu time. It's very distracting as it makes a noise, too. It never used to do it.
No, that looks like CPU hot-plug gone nuts - and I certainly wouldn't expect kill to work on (those) kernel threads.
What has changed ?. Did you do a system update that may have brought in a new kernel or function ?. If so try booting the prior kernel.
Have you recently installed something like KVM or virtualbox ?.
I can't even boot into that kernel now: I get kernel panic, VFS can't mount file system on unknown block (8, 20) and then sched complains about unknown CPU0 being rescheduled. When I get the can't sync message I usually boot into an older kernel and mount the newer partition and then it works when I reboot. Not any more, so I guess I'll try xfs-repair and if that works, I better recompile the kernel.
Hopefully I can thus solve both the failure to sync on boot problem and the unwanted spawn of kworker processes but at this stage any suggestions would be kindly regarded.
Sounds like you have been the instigator of this problem. That being the case it's hard for us to advise, except maybe diff the .config's and investigate.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.