Sorry to budge in. Experiencing the exact same problem on my brand new Samsung Chronos Series 7 using Arch Linux.
Just thought you might be interested in a dirty workaround that takes CPU usage down (at the expense of some problem? dunno, still haven't experienced any): 1 - Locate problematic GPE in /sys/firmware/acpi/interrupts/ (just cat each gpe until you see one with a high interrupt count - mine was gpe13) 2 - execute: echo disable > /sys/firmware/acpi/interrupts/gpexx (substitute for the one you found on the previous step). If that works, you might want to execute it on every system launch (using systemd or whatever ubuntu uses for that) and after resume (I'm using pm-utils for that). I suspect either some driver not playing well or samsung BIOS problem (although I still get it after update) are creating a never-ending interrupt stream. I saw no difference between lsmod when boot worked ok or when the high CPU usage was detected so maybe it is execution-order related? I'm also getting [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear. on boot. This might be related? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1087010 Title: kworker uses 70-90% of a CPU core (hyperthreaded) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1087010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
