https://bugzilla.kernel.org/show_bug.cgi?id=25832 Theodore Tso <tytso@xxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tytso@xxxxxxx --- Comment #6 from Theodore Tso <tytso@xxxxxxx> 2011-02-03 18:22:24 --- I've looked at the kernel log, and the kernel messages displayed, and unfortunately there's no stack trace that would help narrow down what might be going on. Did you have CONFIG_DETECT_SOFTLOCKUP enabled? If not, I would suggest enabling it, and see if you can get a stack trace. Another useful thing to do is to try getting some information via sysrq-l and sysrq-d. Using sysrq-p multiple times to see where the PC is on the various machines can be useful to detect livelocks. Sysrq-t can also be useful, but it's a huge amount of information. In general, for most of the sysrq dumps, you'll really going to need to use a serial console attached to a second computer to record all of this output. So if someone would like to help reproduce this problem. Even if the problem is gone in 2.6.38, it would be useful to see what is going the problem in 2.6.37 so that perhaps the patches could be backported into the stable release if the changes aren't too invasive. So if someone can help us gather this information, it would be really helpful. -- Ted -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
