On Wed, Dec 1, 2010 at 4:43 PM, Daniel Melameth <dan...@melameth.com> wrote: > At this point the CPU is completely utilized, no panic is reported at the > console and the console is unresponsive. Since this is reproducible on all > GENERIC machines I've tried it on, I assume a dmesg is unneeded. I can > reproduce the problem on all 4.8-stable systems I've tried it on and a > recent snapshot.
sending a break over serial or ctrl-alt-esc on keyboard (if ddb.console=1 is enabled) should enable you to get a trace even so.
