Hi Neil,

We are currently using 2.6.36 on a production machine running mdadm, and 
this morning we experienced a very similar issue, but we didn't have the 
LOCKUP_DETECTOR config options set, so there was absolutely no output. 
We also experienced this on a non-production test platform a few days 
ago (same hardware and software as our production machine).

Has this bug been diagnosed/resolved? If so, past which kernel version? 
If not, can you suggest some recourse for us, like perhaps moving back 
to 2.6.35 for our production server, and moving up to the latest stable 
on our test platform, and enabling the LOCKUP_DETECTOR options?

Is this bug totally reproducible Du Jun? If so, should I just try what 
you outlined in your previous message?

Many thanks,
Iordan Iordanov