As someone who *has* been bitten by this bug - by all means.

I'd like to emphasize one more point - we were able to debug it only becaus=
e=20
old kernel at least displayed debug messages. Current kernel deadlocks=20
absolutely dead (pun intended). No output to console, no indication what=20
happens. I consider this regression. If at all possible, we should make sur=
e=20
that console output is available as early as possible.
[ message continues ]

Compile with DISABLE_CONSOLE_SUSPEND set and it should work.

There's a patch queued up for 2.6.24 that adds a command line switch for that.

Greetings,
Rafael
-

[ message continues ]