mouse behaving strange on high cpu load and rapid movements

[Hans Petter Selasky]

On Wednesday 30 September 2009 15:23:18 Alexander Best wrote:
> here's some debug output:
>
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 f6 1a 00 f6 ff 1a 00
> ums_intr_callback:291: x:-10 y:-26 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 fd 19 00 fd ff 19 00
> ums_intr_callback:291: x:-3 y:-25 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 04 18 00 04 00 18 00
> ums_intr_callback:291: x:4 y:-24 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 0b 17 00 0b 00 17 00
> ums_intr_callback:291: x:11 y:-23 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 13 15 00 13 00 15 00
> ums_intr_callback:291: x:19 y:-21 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 16 12 00 16 00 12 00
> ums_intr_callback:291: x:22 y:-18 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 1c 0e 00 1c 00 0e 00
> ums_intr_callback:291: x:28 y:-14 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 54 c5 00 54 00 c5 ff
> ums_intr_callback:291: x:84 y:59 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 fb f8 00 fb ff f8 ff
> ums_intr_callback:291: x:-5 y:8 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 fd fa 00 fd ff fa ff
> ums_intr_callback:291: x:-3 y:6 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 fe fc 00 fe ff fc ff
> ums_intr_callback:291: x:-2 y:4 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 ff fd 00 ff ff fd ff
> ums_intr_callback:291: x:-1 y:3 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 00 ff 00 00 00 ff ff
> ums_intr_callback:291: x:0 y:1 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 00 ff 00 00 00 ff ff
> ums_intr_callback:291: x:0 y:1 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 00 01 00 00 00 01 00
> ums_intr_callback:291: x:0 y:-1 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 00 01 00 00 00 01 00
> ums_intr_callback:291: x:0 y:-1 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 ff 01 00 ff ff 01 00
> ums_intr_callback:291: x:-1 y:-1 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 00 03 00 00 00 03 00
> ums_intr_callback:291: x:0 y:-3 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 ff 03 00 ff ff 03 00
> ums_intr_callback:291: x:-1 y:-3 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 ff 03 00 ff ff 03 00
> ums_intr_callback:291: x:-1 y:-3 z:0 t:0 w:0 buttons:0x00000000
> ums_intr_callback:207: sc=0xc95f1800 actlen=8
> ums_intr_callback:225: data = 00 ff 00 00 ff ff 00 00
> ums_intr_callback:291: x:-1 y:0 z:0 t:0 w:0 buttons:0x00000000
>

The debug trace looks normal. Maybe there is a bug in your mouse, if your CPU 
is so busy that there is no bandwidth left for the USB hostcontroller 
schedule.

--HPS