I'm using Debian Sid with Linux kernel 3.3.0-trunk (3.3.2-experimental) and I've noticed that kworker/u:7 uses up to 30% CPU resources and the last time I've tried 3.3.0-rc6, kworker/u:1 uses up to 20% in one of two CPU cores. I don't know what is causing it, so according to the article with noacpi or acpi=off
, since I've set acpi=off in /etc/default/grub, I thought this might solve my problem.
For some reason, I can't SSH into my Debian server, probably because the kernel got hang up? I've just made a mistake as I'm unsure if very new computers need ACPI to function. Do they?
I mean, what is causing kworker/u:7 or kworker/u:1 to use up a lot of CPU resources? Linux 3.3.0-trunk did work when kworker is not using any CPU resources, but after a few minutes after reboot (maybe around 10 to 20 minutes? I don't know), it does.