3 ms·
Something hanging is not automatically a "deadlock". If you jiggle it and starts moving again, that tends to be evidence against the deadlock hypothesis. It co
by kazinator 4y ago
Something hanging is not automatically a "deadlock". If you jiggle it and starts moving again, that tends to be evidence against the deadlock hypothesis. It could be a lost wakeup problem. If something is blocked on a write due to a lost wakeup problem, what it means is that the task was preparing to block a due to no buffer space just around the moment when space became available. Due to a race condition, it blocked anyway, missing the "buffer available" event.
Lost wakeup problems are more readily susceptible to recovery by "jiggling" the situation than deadlocks. If there is a deadly embrace situation, and you randomly wake up some involved task (in such a way that it doesn't just error out) it will typically just spin around and wait again, re-engaging with the deadlock. You can interrupt deadlocks in a breakpoint debugger, and when you hit "go" again, the deadlock typically continues.