Matthias Buelow <mkb@mukappabeta.de>  wrote:
 > Sorry, with "completely unresponsive", I meant user process space
 > of course (like, machine is overloaded and trashing along or somesuch).
 > The kernel interrupt routines, which ultimately map onto the console
 > driver (which would recognize the keystrokes and initiate the reboot)
 > are always kindof realtime and thus would not be affected.

Personally, I don't see the point of having a special 'reboot'
key sequence... When a machine is wedged/unresponsive, you either
pop into the debugger to figure out why so it doesn't happen 
again, or you hit reset.

You can always reboot from ddb too. So you have to type 'reboot', no 
big deal.