INFO: task kworker blocked for more than 120 seconds

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

# The stack trace under the message shows what it was waiting for
dmesg -T | grep -A20 "blocked for more than"

# Which processes are in D state right now?
ps -eo pid,stat,wchan:32,cmd | awk '$2 ~ /D/'

# Is a disk saturated (util near 100%, high await)?
iostat -xz 2 5

# Hung network mounts show up here
mount -t nfs,nfs4,cifs; timeout 5 stat /mnt/share || echo "mount not responding"

# Large writeback stalls: flush earlier and in smaller chunks
sysctl vm.dirty_ratio vm.dirty_background_ratio
sudo sysctl -w vm.dirty_background_bytes=268435456 vm.dirty_bytes=1073741824

How to diagnose Performance errors

Performance failures rarely produce an error message. They produce timeouts elsewhere. The three classic causes are stop-the-world garbage collection, thread pool starvation (all workers blocked on I/O so new requests queue), and event loop blocking in single-threaded runtimes. All three look identical from outside: latency climbs, then upstream timeouts fire. Distinguishing them requires looking inside the process.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

1. Measure the p99, not the mean. Averages hide exactly the pauses that cause timeouts.
2. For the JVM, enable GC logging (-Xlog:gc*) and correlate pause durations with latency spikes before tuning anything.
3. For thread pools, log active versus queued task counts. A queue that grows while CPU is idle is starvation, and the fix is asynchronous I/O, not more threads.
4. In Node.js, measure event loop lag directly (perf_hooks.monitorEventLoopDelay). Any synchronous work over a few milliseconds per request will show up here.
5. Profile before optimising. pprof, async-profiler, py-spy and Chrome's profiler all point at the real hot path, which is rarely where intuition suggests.

Tools worth reaching for

• async-profiler
• go tool pprof
• py-spy
• perf_hooks.monitorEventLoopDelay
• -Xlog:gc*

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

📖 docs.kernel.org 📖 docs.kernel.org

Related Performance errors

• Connections hang or reset with ListenOverflows increasingThe kernel finished the handshake but the application was too slow to call accept(), so the…
• Container CPU throttling: nr_throttled rising in cpu.statA CPU limit is enforced as a quota per 100ms period, so a process that spends its quota early…
• CPU0: Core temperature above threshold, cpu clock throttledThe CPU hit its thermal limit and the hardware cut its clock speed to cool down. Everything…
• First requests after a deploy are slow, then it settlesA freshly started process serves unoptimised code until the JIT has enough samples, with…
• Go: high tail latency in a container, GOMAXPROCS above the CPU limitBefore Go 1.25, GOMAXPROCS defaulted to the number of CPUs on the node and ignored the…
• High iowait: load average climbing while the CPU sits idleLinux counts tasks in uninterruptible sleep towards the load average, so processes blocked on…
• java.lang.OutOfMemoryError: GC overhead limit exceededThe JVM spent over 98 percent of recent time collecting and recovered less than 2 percent of…
• JVM: pause with no GC in the log (long time to safepoint)A safepoint stops every application thread, and the pause includes however long the slowest…

See all 19 Performance errors →

Browse other categories

• HTTP 494xx client errors, 5xx server errors, redirects, headers and protocol problems.
• JavaScript 42npm resolution, async pitfalls, hydration, memory limits and runtime type…
• Database 41Connections, deadlocks, constraints, replication and memory limits.
• AI 35Rate limits, context windows, GPU memory and model-serving failures.
• Network 35Refused connections, timeouts, resets, MTU problems and port exhaustion.
• Python 35Imports, virtual environments, encoding, concurrency and dependency conflicts.
• Kubernetes 34CrashLoopBackOff, ImagePullBackOff, OOMKilled, RBAC, scheduling and storage.
• Docker 27Daemon connectivity, disk space, image pulls, ports and architecture mismatches.
• System 26Disk space, systemd units, file descriptors, OOM killer and scheduled jobs.
• Cloud 25IAM permissions, quotas, service limits and credential failures.
• Security 25JWT validation, CSRF, OAuth grants, SELinux, SSH host keys and CSP.
• TLS 24Untrusted authorities, expiry, hostname mismatch, chains and cipher negotiation.

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.