Bug ID: 83911 Summary: Thermaltake USB Gaming Mouse not working

Hi all,
I was asked to send you a bug report I just submit so here we are :
the bug is there  https://bugzilla.kernel.org/show_bug.cgi?id=83911. 

I reproduce it here : 

I have a usb mouse model : TT esport Sapphira, from thermaltake.


When I plug it in I have this kernel messages

[ 1019.645758] usb 1-1.6.2: new full-speed USB device number 8 using ehci-pci
[ 1019.741008] usb 1-1.6.2: New USB device found, idVendor=04f2, 
idProduct=1106
[ 1019.741016] usb 1-1.6.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[ 1019.741020] usb 1-1.6.2: Product: USB Gaming Mouse
[ 1019.741024] usb 1-1.6.2: Manufacturer: Thermaltake
[ 1019.742903] input: Thermaltake USB Gaming Mouse as 
/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0/input/input23
[ 1019.743530] hid-generic 0003:04F2:1106.0006: input,hidraw1: USB HID v1.11 
Mouse [Thermaltake USB Gaming Mouse] on usb-0000:00:1a.0-1.6.2/input0
[ 1019.747180] input: Thermaltake USB Gaming Mouse as 
/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.1/input/input24
[ 1019.749302] hid-generic 0003:04F2:1106.0007: input,hiddev0,hidraw2: USB HID 
v1.11 Keyboard [Thermaltake USB Gaming Mouse] on usb-0000:00:1a.0-1.6.2/input1

So the usb mouse is properly identify but that's about it. Nothing more,the 
mouse is not powered (non of the led-light neither the laser produce light) 
and of course neither clicking or moving the mouse do anything.

To add to the confusion in rare occasions, ( +/- 3 times in one month of using 
the computer each day) it get powered and works correctly. One time it 
occurred  I checked the modules loaded and  messages from the kernel but I did 
not find anything relevant. 
I normally use occurs a kernel 3.13.0-24-generic of Linux mint package (aka 
Ubuntu kernel), but I tested as well with the last kernel from git which was 
at the time 3.17-rc3 and the problem was still there.

Attached a lsmod result.

Ps: I know I use nvidia binary  but this problem happened before, so please 
just ignore it.