No, this is different totally.

With a button, a button down code is sent and a button up code is sent. The player software does the autorepeat if it gets a down and not an up. The bug appears to be that the main CPU doesn't see the button up and so keeps repeating.

The rotary control sends one code for clockwise & one for anticlockwise. If the CPU misses either of these, the worst that happens is that the one click goes missing - there's no runaway condition. The Mk2 buttons also send two up codes on every button release to try to ensure that at least one gets caught. We're still investigating the missing of buttons, using a patched kernel to look at times when IRQs are disabled (which can cause a button to get missed).

Hugo