Ok, this is a known bug: it happens with all keys that send 2 keycodes

(the num-pad ENTER, cursor keys etc) and has to do with the fact that

the keyboard controller never gets an accnowledgement for them both, so

it doesn't interrupt when the next keys are pressed - thus linux won't

read the enter (or any other key) when the bootimage has been put in.
I don't know any fast fix: I haven't looked into it. It's probably a
I think this is a problem with ash and the termios interface. ash

probably sets the back-space key to something else than \177. I dunno:

haven't used ash. Get bash, and this (and other problems) will go away
Ok, this is a real bug: the keyboard interrupts happen too fast for all

the information to be printed, and the kernel stack gets overcrowded:

reboot. The easy solution is not to do this, the more complete solution

is to put some kind of lock on the info-key. I'll look into it.
                Linus