Comment 53 for bug 330824

Saivann,

The screen shot is very much appreciated, but unfortunately sysrq-w generates a *huge* amount of data; much more than can fit on a single screen, alas. Which means to get the full sysrq-w, we would either need to get you set up with a serial console, and then monitor the output via the serial console to record all of the data dumped out to the console, OR, if you can get a separate root partition and test partition, and replicate the hang on the test partition, hopefully writes to the root partition will still work. At that point, you might be able to do "dmesg > /dmesg.txt", and thus save the output of the sysrq-w.

One other thought --- does the Ubuntu kernel come with CONFIG_LOCKDEP and CONFIG_LOCKDEP_SUPPORT enabled? It may be that this will give us the warning we need, hopefully a little bit more succintly. If someone can reproduce the problem on a custom-made kernel that has Lockdep enabled, maybe that will shed some light on what's going on.