Hi, In order for the issue described here to be properly handled, some logs are needed. https://wiki.ubuntu.com/Kernel/Bugs
As you can see from the links, as a last resort, at a minimum, your bug report should contain the output of the following commands: $ uname -a > uname-a.log $ cat /proc/version_signature > version.log $ dmesg > dmesg.log $ sudo lspci -vvnn > lspci-vvnn.log Related to your issue, to find out why a kworker is wasting your CPU, you can create CPU backtraces: watch your processor load (with top or something) and in moments of high load through kworker, execute sudo -s echo l > /proc/sysrq-trigger to create a backtrace. Do this several times, then watch the backtraces at the end of dmesg output. See what happens frequently in the CPU backtraces, it hopefully points you to the source of your problem. (you can check this link http://askubuntu.com/questions/33640/kworker-what-is-it-and-why-is-it- hogging-so-much-cpu) ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536766 Title: 14.04 on kernel 4.3: kworker/ksoftirqd consume 100% CPU until a USB device is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1536766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
