kworker high CPU
kworker threads are the kernel's general-purpose workers. When they become the top CPU consumers, something is driving kernel-level work hard.
Common symptoms
- kworker processes appear at the top of process lists
- CPU seems high but no user app is obviously responsible
- Load correlates with disk or network activity
Likely causes
- Heavy disk IO operations
- Network interrupt processing
- Filesystem journaling or metadata activity
- Hardware interrupt storms
Evidence to look for
kworker threads dominate CPU
IO metrics rise during kworker spikes
Interrupt counts climb
What it usually means
kworker CPU is usually a downstream symptom of heavy IO or driver activity rather than a bug in kworker itself.
What to do next
- 1Check disk and network IO first
- 2Look for interrupt storms or driver issues
- 3Profile kernel stacks to identify the specific work
See what's causing your CPU
cpum.ai turns CPU, process, disk, and memory signals into plain-English explanations with evidence.
Open cpum.ai