Bug 869460 - "Weird" mouse (using ehci_hcd) story on Asus K52Jc laptop
"Weird" mouse (using ehci_hcd) story on Asus K52Jc laptop
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-23 21:24 EDT by Michal Jaegermann
Modified: 2013-03-03 20:15 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-03-03 20:15:20 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2012-10-23 21:24:39 EDT
Description of problem:

I recently got a wireless USB mouse which works just fine on other machines with Fedora 16 (tested on one desktop and one Eee netbook), and also on another desktop with CentOS6, but it absolutely refuses to move a pointer and/or register clicks when used with K52Jc.

When attached the following shows up in dmesg:

[ 4937.292735] usb 2-1.3: new full-speed USB device number 12 using ehci_hcd
[ 4937.380431] usb 2-1.3: New USB device found, idVendor=1d57, idProduct=0016
[ 4937.380439] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4937.380444] usb 2-1.3: Product: HID Wireless Mouse
[ 4937.380448] usb 2-1.3: Manufacturer: HID Wireless Mouse
[ 4937.383626] input: HID Wireless Mouse HID Wireless Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/input/input13
[ 4937.384492] hid-generic 0003:1D57:0016.0005: input,hidraw0: USB HID v1.10 Mouse [HID Wireless Mouse HID Wireless Mouse] on usb-0000:00:1d.0-1.3/input0

For comparison this is a similar dmesg fragment from Eee:

[  111.017280] usb 2-2: new full-speed USB device number 2 using uhci_hcd
[  111.185229] usb 2-2: New USB device found, idVendor=1d57, idProduct=0016
[  111.185247] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  111.185259] usb 2-2: Product: HID Wireless Mouse
[  111.185271] usb 2-2: Manufacturer: HID Wireless Mouse
[  111.195711] input: HID Wireless Mouse HID Wireless Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input11
[  111.198535] hid-generic 0003:1D57:0016.0001: input,hidraw0: USB HID v1.10 Mouse [HID Wireless Mouse HID Wireless Mouse] on usb-0000:00:1d.0-2/input0

Both look pretty much the same with this exception that on Eee the mouse goes through uhci_hcd and works and it is ehci_hcd with K52Jc.  On both desktops I see "using ohci_hcd" for a change.

Version-Release number of selected component (if applicable):
kernel-3.6.2-1.fc16.x86_64 and all earlier ones I had tried

How reproducible:
always

Additional info:
I have some other USB mice, wired and wireless, and they work on K52Jc even if they show up as ehci_hcd; for example like this:

[ 1386.089875] usb 2-1.3: new low-speed USB device number 11 using ehci_hcd
[ 1386.168947] usb 2-1.3: New USB device found, idVendor=093a, idProduct=2510
[ 1386.168955] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1386.168960] usb 2-1.3: Product: USB OPTICAL MOUSE
[ 1386.168964] usb 2-1.3: Manufacturer: PIXART
[ 1386.174269] input: PIXART USB OPTICAL MOUSE as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/input/input12
[ 1386.174895] hid-generic 0003:093A:2510.0004: input,hidraw0: USB HID v1.11 Mouse [PIXART USB OPTICAL MOUSE] on usb-0000:00:1d.0-1.3/input0


So in that sense this is not "critical" until I will find myself somewhere with only one mouse which will happen not to work.  Still any ideas what is going on here and how I can find more?
Comment 1 Michal Jaegermann 2013-03-03 20:15:20 EST
I tried again with kernel-3.8.1-201.fc18.x86_64 and, although the mouse looks really the same in dmesg output, this time it works.  No idea what is the real difference.

Note You need to log in before you can comment on or make changes to this bug.