On Thu, Jun 09, 2011 at 09:30:35PM -0400, John David Anglin wrote: > As far as I can tell, all are stuck in the kernel. Gdb can't step > the code, nor do breaks on the next instruction ever get hit. This > may have something to do with the fact that the instruction is trying > to read from text (C switch statement). sysrq-l will show a backtrace for all CPUs. That might be helpful in diagnosing this problem. -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
