Hi Oliver thank you for your reply.
Apologies for now replying from gmail. I'm being told my crjb.net
address is failing SPF and that I have to shoehorn this email into
plain-text for you. Here we go :)
I must correct/clarify that the browser forward and back buttons seem to
work in chrome and that in testing this evening, they have not frozen or
crashed anything. The output I provided before was simply the dmesg
record of the mouse being detected on boot or plugin, not any dmesg
records produced on the depression of the buttons of concern (which are
primarily the DPI+ and DPI- buttons).
*Relevant output from usbmon (cat /sys/kernel/debug/usb/usbmon/0u)*
I was able to capture my pressing the dpi+ button twice before the mouse
driver crashed.
ffffa0b1fca52240 1143494193 C Ii:1:015:2 0:1 8 = 00000000 00000000
ffffa0b1fca52240 1143494212 S Ii:1:015:2 -115:1 8 <
ffffa0b1fca52240 1144099217 C Ii:1:015:2 0:1 8 = 00000000 00000000
ffffa0b1fca52240 1144099233 S Ii:1:015:2 -115:1 8 <
*From lsusb*
Bus 001 Device 015: ID 1044:7a13 Chu Yuen Enterprise Co., Ltd
*From cat /sys/kernel/debug/usb/devices*
T: Bus=01 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#= 15 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=1044 ProdID=7a13 Rev= 2.00
S: Manufacturer=Texas Instruments
S: Product=MSP430-USB Mouse
S: SerialNumber=8C2F0C5132000C00
C:* #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=15ms
E: Ad=01(O) Atr=03(Int.) MxPS= 8 Ivl=15ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid
E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=1ms
E: Ad=02(O) Atr=03(Int.) MxPS= 8 Ivl=1ms
I:* If#= 2 Alt= 0 #EPs= 2 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid
E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=20ms
E: Ad=03(O) Atr=03(Int.) MxPS= 8 Ivl=20ms
I:* If#= 3 Alt= 0 #EPs= 2 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid
E: Ad=84(I) Atr=03(Int.) MxPS= 64 Ivl=1ms
E: Ad=04(O) Atr=03(Int.) MxPS= 64 Ivl=1ms
Unplugging and re-plugging the mouse in, it moves to Bus 01, Device 16
and I captured the following:
*usbmon output from the DPI - button*
ffffa0b20247ab40 1348549098 C Ii:1:016:2 0:1 8 = 00000000 00000000
ffffa0b20247ab40 1348549123 S Ii:1:016:2 -115:1 8 <*
*
I can confirm that while the mouse cursor became unresponsive/frozen on
the computer after pressing this button, when I re-inserted it in, the
mouse movement across the screen reflected that the DPI - button had
been pressed, as it was sluggish now. So at least the device is
reflecting the button being pressed and is responding as such.
*usbmon output from the browser-forward button*
I pressed thus button three times and the mouse appears to still work!
(of course we're now at bus 01, device 017
ffffa0b25856b980 1565643086 C Ii:1:017:2 0:1 8 = 10000000 00000000
ffffa0b25856b980 1565643113 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1565810091 C Ii:1:017:2 0:1 8 = 00000000 00000000
ffffa0b25856b980 1565810113 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1566953154 C Ii:1:017:2 0:1 8 = 10000000 00000000
ffffa0b25856b980 1566953181 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1567113163 C Ii:1:017:2 0:1 8 = 00000000 00000000
ffffa0b25856b980 1567113185 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1567762196 C Ii:1:017:2 0:1 8 = 10000000 00000000
ffffa0b25856b980 1567762215 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1567890202 C Ii:1:017:2 0:1 8 = 00000000 00000000
ffffa0b25856b980 1567890225 S Ii:1:017:2 -115:1 8 <
*usbmon output from the browser-backward button*
still not frozen ...
ffffa0b25856b980 1710325920 C Ii:1:017:2 0:1 8 = 000000ff ff000000
ffffa0b25856b980 1710325950 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1710343901 C Ii:1:017:2 0:1 8 = 08000000 00000000
ffffa0b25856b980 1710343919 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1710506929 C Ii:1:017:2 0:1 8 = 00000000 00000000
ffffa0b25856b980 1710506952 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1710609934 C Ii:1:017:2 0:1 8 = 08000000 00000000
ffffa0b25856b980 1710609956 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1710720943 C Ii:1:017:2 0:1 8 = 00000000 00000000
ffffa0b25856b980 1710720965 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1710981955 C Ii:1:017:2 0:1 8 = 08000000 00000000
ffffa0b25856b980 1710981977 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1711079959 C Ii:1:017:2 0:1 8 = 00000000 00000000
ffffa0b25856b980 1711079981 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1711615989 C Ii:1:017:2 0:1 8 = 08000000 00000000
ffffa0b25856b980 1711616014 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1711730998 C Ii:1:017:2 0:1 8 = 00000000 00000000
ffffa0b25856b980 1711731020 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1712017010 C Ii:1:017:2 0:1 8 = 08000000 00000000
ffffa0b25856b980 1712017033 S Ii:1:017:2 -115:1 8 <
ffffa0b25856b980 1712089016 C Ii:1:017:2 0:1 8 = 00000000 00000000
ffffa0b25856b980 1712089038 S Ii:1:017:2 -115:1 8 <
Pressing the DPI+ button made the mouse cursor unresponsive to movement,
however after re-inserting it, the mouse's movement did reflect that the
DPI+ switch had been pressed.
Hope this helps.
Regards
Christian
On 25/09/17 22:22, Oliver Neukum wrote:
Am Sonntag, den 24.09.2017, 13:14 +1000 schrieb Christian Bullow:
Upon depressing the DIP switch or forward/backward buttons, the mouse
freezes and is unresponsive. The only way to fix this is my unplugging
it, and putting it into a /different/ USB port.
I am happy to be guided as to how to inform you of the issue and/or
capture the messaging from the mouse buttons.
*dmesg output*
[ 1386.760402] usb 1-1.1: USB disconnect, device number 3
[ 1389.758884] usb 1-1.1: new full-speed USB device number 4 using ehci-pci
[ 1389.872812] usb 1-1.1: New USB device found, idVendor=1044,
idProduct=7a13
[ 1389.872816] usb 1-1.1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 1389.872818] usb 1-1.1: Product: MSP430-USB Mouse
[ 1389.872820] usb 1-1.1: Manufacturer: Texas Instruments
[ 1389.872822] usb 1-1.1: SerialNumber: 8C2F0C5132000C00
[ 1389.903323] input: Texas Instruments MSP430-USB Mouse as
/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:1044:7A13.0007/input/input27
[ 1389.963586] hid-generic 0003:1044:7A13.0007: input,hidraw0: USB HID
v1.01 Keyboard [Texas Instruments MSP430-USB Mouse] on
usb-0000:00:1a.0-1.1/input0
[ 1389.966651] input: Texas Instruments MSP430-USB Mouse as
/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.1/0003:1044:7A13.0008/input/input28
[ 1390.027363] hid-generic 0003:1044:7A13.0008: input,hidraw2: USB HID
v1.01 Mouse [Texas Instruments MSP430-USB Mouse] on
usb-0000:00:1a.0-1.1/input1
[ 1390.031052] input: Texas Instruments MSP430-USB Mouse as
/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.2/0003:1044:7A13.0009/input/input29
[ 1390.091874] hid-generic 0003:1044:7A13.0009: input,hiddev0,hidraw3:
USB HID v1.01 Mouse [Texas Instruments MSP430-USB Mouse] on
usb-0000:00:1a.0-1.1/input2
[ 1400.113061] hid-generic 0003:1044:7A13.000A: timeout initializing reports
[ 1400.113386] hid-generic 0003:1044:7A13.000A: hiddev0,hidraw5: USB HID
v1.01 Device [Texas Instruments MSP430-USB Mouse] on
usb-0000:00:1a.0-1.1/input3
Hi,
this dmesg as such is pretty uninformative. Is that what you get as you
plug in the mouse or as you push the button? If the latter, we will
need a usbmon trace.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
