The hung_task timer fired on a task, but there are much older blocked tasks - why didn't they trip hung_task timer?
Issue
- One process tripped hung_task since it was in D-state (uninterruptible sleep - 'UN') for longer than hung_task_timeout_secs. However, there were other processes blocked in the D-state for much longer time. Why didn't the oldest task trip the hung task timer?
- System panics with
Kernel panic - not syncing: hung_task: blocked tasksbut the task listed is not the oldest task. - How does the hung_task timer decide which task to check?
Environment
- Red Hat Enterprise Linux
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
