6.2-STABLE deadlock?

[Eugene Grosbein]

Kostik Belousov wrote:

> I would suspect the mlx controller. There is several processes (for instance,
> 988, 50918) waiting for completion of block read, and processes in the "ufs"
> states are the result of the lock cascade, IMHO.

It may be possible that controller is not guilty.

You can easily reproduce lock in "ufs" state with commands from
the "How-To-Repeat" section of:
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/107439

The PR is closed but the problem still exists in recent 6.2-STABLE.
GENERIC has the problem too, GENERIC+INVARIANTS panices at once
instead of producing locked processes.

Eugene Grosbein.