Comment 28 for bug 636091

Ok, I managed to get something if I hold a key on the affected laptop, and run the command from ssh on another machine as soon as the characters stop appearing on screen; I've attached a copy of /var/log/syslog which contains a couple of occurrences I tried to trap, to give the best chance of identifying what was going wrong.

I don't know too much about the kernel but if it hangs on the local keyboard and in the SSH session (as well as much everything else), and finally does show the characters I "typed" once it unlocks, wouldn't the sysrq results also be generated and outputted after the unlock, and thus not accurately represent the issue?