Bug 840391
| Summary: | wireless mouse works only through hub | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | kpijarski <kpijarski> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | bird98, btissoir, dennis, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mschmidt, robert |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | hid logitec_dj first=3.2 tested=3.4.4-5 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-11 01:22:01 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
kpijarski
2012-07-16 08:51:13 UTC
This report in Ubuntu looks like a similar problem: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971854 Somebody there suggested a workaround: modprobe -r hid_logitech_dj modprobe -r usbhid modprobe usbhid It would be useful to know if it helps. Your problem may be resolved faster if you could test whether the bug happens also with a current upstream kernel from Linus's git tree and then posting about your problem to the upstream linux-input mailing list: http://vger.kernel.org/vger-lists.html#linux-input (or maybe to linux-usb). hello michal, thanks for you quick reply - yes, it does seem this is the same bug, but the workaround doesn't work, unfortunately. unloading hid_logitech_dj work fine, but trying to remove usbhid results in the foolowing message: libkmod: kmod_module_get_holders: could not open '/sys/module/usbhid/holders': No such file or directory Error: Module usbhid is in use as to the upstream kernel - i did compile my own kernel once or twice (on ubuntu), but i have no idea how to go about compiling a kernel from git. any reasonable how-tos out there? Thanks! ok, i think this is the relevant launchpad bug fot this issue: https://bugs.launchpad.net/ubuntu/+bug/958174 there also is an appropriate kernel bug filed for this issue: https://bugzilla.kernel.org/show_bug.cgi?id=43631 does this seem right? According to the launchpad bug, this is a regression introduced by commit 4ea5454203d991ec upstream. Seems logitech is working on a fix. We'll monitor. Hello guys, I just installed FC17 on a brand new Vaio S (japanese version) and I found the following, which appears to be related to this. 1. I could not get the NetworkManager to work (it would actually semi-hang the box , unless I removed and blacklisted the "sierra" module) 2. After I got that working, I plugged in my Logitech wireless USB mouse, and it was working fine, until I did a yum upgrade. current kernel: 3.6.10-2.fc17.i686.PAE #1 SMP Tue Dec 11 18:27:35 UTC 2012 i686 i686 i386 GNU/Linux the error I got in /var/log/messages is: Dec 28 22:36:38 yuko kernel: [ 1072.671312] logitech-djreceiver 0003:046D:C52B.0006: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-3/input2 Dec 28 22:36:38 yuko kernel: [ 1072.671592] logitech-djreceiver 0003:046D:C52B.0006: logi_dj_probe:logi_dj_recv_query_paired_devices error:-32 Dec 28 22:36:38 yuko kernel: [ 1072.672389] logitech-djreceiver: probe of 0003:046D:C52B.0006 failed with error -32 after doing: modprobe -r hid_logitech_dj modprobe -r usbhid modprobe usbhid then replugging the mouse I still got zilch, no response, Then I did a modprobe hid_logitech_dj Now my mods looklike this: [root@yuko ~]# lsmod | grep usb btusb 23199 0 bluetooth 275642 24 bnep,btusb,rfcomm [root@yuko ~]# lsmod | grep logi hid_logitech_dj 18173 0 Then I changed the little wireless usb dongle from one port to another, and voilla mouse is working as reported by the messages file: Dec 28 22:36:47 yuko kernel: [ 1081.418364] usb 3-3: USB disconnect, device number 3 Dec 28 22:36:55 yuko kernel: [ 1089.402670] usb 3-1: new full-speed USB device number 4 using xhci_hcd Dec 28 22:36:55 yuko kernel: [ 1089.416257] usb 3-1: New USB device found, idVendor=046d, idProduct=c52b Dec 28 22:36:55 yuko kernel: [ 1089.416265] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Dec 28 22:36:55 yuko kernel: [ 1089.416269] usb 3-1: Product: USB Receiver Dec 28 22:36:55 yuko kernel: [ 1089.416272] usb 3-1: Manufacturer: Logitech Dec 28 22:36:55 yuko kernel: [ 1089.422906] logitech-djreceiver 0003:046D:C52B.0009: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-1/input2 Dec 28 22:36:55 yuko kernel: [ 1089.425089] input: Logitech Unifying Device. Wireless PID:400a as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.2/0003:046D:C52B.0009/input/input13 Dec 28 22:36:55 yuko kernel: [ 1089.425353] logitech-djdevice 0003:046D:C52B.000A: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:400a] on usb-0000:00:14.0-1:1 Dec 28 22:36:55 yuko mtp-probe: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1" Dec 28 22:36:55 yuko mtp-probe: bus: 3, device: 4 was not an MTP device this is my lsusb: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 08ff:168f AuthenTec, Inc. Bus 001 Device 004: ID 8087:07d6 Intel Corp. Bus 001 Device 005: ID 0489:d601 Foxconn / Hon Hai Bus 001 Device 006: ID 1199:68a2 Sierra Wireless, Inc. Bus 001 Device 007: ID 0489:e04d Foxconn / Hon Hai ---------- p.s.: about the sierra mod, well the machine would not go past the login, i.e. no gnome, nothing , and I noticed the sierra messages on the black screen of forever-wait: Dec 29 02:08:52 yuko kernel: [ 9.587568] sierra: v.1.7.16:USB Driver for Sierra Wireless USB modems Dec 29 02:08:56 yuko kernel: [ 18.351839] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8 Dec 29 02:08:56 yuko kernel: [ 18.352408] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8 Dec 29 02:08:56 yuko kernel: [ 18.352954] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8 Dec 29 02:08:56 yuko kernel: [ 18.353486] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8 so I went into recovery mode (fancy word for singleuser i guess lol) and blacklisted the sierra mod. p.s.: only win8 the machine saw was the UEFI boot screens in japanese which i had to decode with my wife's help, until i got to the BIOS and was able to set up legacy boot mode and wipe the beast clean. Update: I was able to reproduce this problem in my other new Vaio Z. And I also seem to have found a "fix". If I unplug and replug the small dongle on the computer, while the mouse is "switched on" then the problem always happens (error -32) But, if I turn off the mouse before plugging the dongle back in, and once plugged in, then everything works fine "as advertised". I hope this kicks the ball into logitech/user court. cheers The problem has been reported upstream only yesterday :( Here is my answer and an attempt to fix the problem (which seems hardware related): https://patchwork.kernel.org/patch/2125381/ To sum up, the USB3 interfere with the receiver, and the command is not correctly sent. The driver should not give up in such cases and try later to re-probe the mouse. Cheers, Benjamin *** Bug 904875 has been marked as a duplicate of this bug. *** The fix has been accepted upstream: https://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.9/upstream-fixes&id=dcd9006b1b053c7b1cebe81333261d4fd492ffeb It will be pushed into 3.9 and be sent to stable as soon as it lands into Linus' tree. Patch applied to F17/F18. Rawhide should pick it up naturally. Thanks Benjamin. kernel-3.8.2-206.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/kernel-3.8.2-206.fc18 kernel-3.8.2-105.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.8.2-105.fc17 Package kernel-3.8.2-206.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.8.2-206.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3630/kernel-3.8.2-206.fc18 then log in and leave karma (feedback). kernel-3.8.2-206.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. kernel-3.8.2-105.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2013-3638/kernel-3.8.2-105.fc17 kernel-3.8.3-101.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.8.3-101.fc17 kernel-3.8.3-103.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |