On Wed, Dec 1, 2010 at 3:55 PM, Ted Unangst <ted.unangst@gmail.com> wrote:
quoted text
> On Wed, Dec 1, 2010 at 4:43 PM, Daniel Melameth <daniel@melameth.com>
wrote:
quoted text
>> 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
quoted text
>> 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.

The machine is unresponsive.  Ctrl-Alt-Esc with ddb.console=1 gets me
nowhere when this happens and, perhaps it's my machines or the machine
I'm using as a serial console, but sending a BREAK over serial doesn't
seem to get me into ddb either.