Bug 43631 - Problem: USB Mouse inactive when starting system, keyboard fine
Summary: Problem: USB Mouse inactive when starting system, keyboard fine
Status: RESOLVED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_input-devices
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-21 04:22 UTC by John
Modified: 2013-07-01 21:37 UTC (History)
8 users (show)

See Also:
Kernel Version: 3.4 (3.0 or so + ?)
Subsystem:
Regression: No
Bisected commit-id:


Attachments
As requested by Nestor here is a dmesg file when the issue happened (550.35 KB, text/plain)
2012-06-29 08:38 UTC, John
Details
logitech fix (4.36 KB, application/octet-stream)
2012-08-08 02:03 UTC, John
Details

Description John 2012-06-21 04:22:41 UTC
Hello,

*Sometimes* when X starts it does detect the mouse as seen in the log
but when I move it nothing happens on screen, and doing a cat on the
/dev/input/eventX does not produce anything either when moving the
mouse.

To get the mouse to work, most of the time I have to unplug the USB
adapter and replug it, although sometimes I need to switch it with the
keyboard USB adapter.
I am not sure why and how as it does not always happen.
I know of at least one other person with similar symptoms.

As for my configuration, I am running Arch Linux with a 3.4 Linux
kernel, xorg-server 1.12.2, evdev 2.7.0.
My mouse is a Logitech performance MX with a USB wireless unifying receiver.
My keyboard is a diNovo keyboard with a USB bluetooth receiver.
Xorg is auto-started by kdm which is started by systemd.

Here is my Xorg log: http://pastebin.com/pWnHwF2d
In this one I cold started the computer, then got no mouse so I
unplugged / replugged the receiver but nothing so then I switched they
keyboard and mouse receivers and then it worked. Everything was
working fine before shutting down the computer though.

Thank you,
John
Comment 1 Dmitry Torokhov 2012-06-26 18:40:35 UTC
On Thursday, June 21, 2012 04:22:42 AM bugzilla-daemon@bugzilla.kernel.org 
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=43631
> 
>            Summary: Problem: USB Mouse inactive when starting system,
>                     keyboard fine
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 3.4 (but happened with previous kernels too, maybe all
>                     the way to 3.0 or so)
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Input Devices
>         AssignedTo: drivers_input-devices@kernel-bugs.osdl.org
>         ReportedBy: john.ettedgui@gmail.com
>         Regression: No
> 
> 
> Hello,
> 
> *Sometimes* when X starts it does detect the mouse as seen in the log
> but when I move it nothing happens on screen, and doing a cat on the
> /dev/input/eventX does not produce anything either when moving the
> mouse.
> 
> To get the mouse to work, most of the time I have to unplug the USB
> adapter and replug it, although sometimes I need to switch it with the
> keyboard USB adapter.
> I am not sure why and how as it does not always happen.
> I know of at least one other person with similar symptoms.
> 
> As for my configuration, I am running Arch Linux with a 3.4 Linux
> kernel, xorg-server 1.12.2, evdev 2.7.0.
> My mouse is a Logitech performance MX with a USB wireless unifying receiver.
> My keyboard is a diNovo keyboard with a USB bluetooth receiver.
> Xorg is auto-started by kdm which is started by systemd.
> 
> Here is my Xorg log: http://pastebin.com/pWnHwF2d
> In this one I cold started the computer, then got no mouse so I
> unplugged / replugged the receiver but nothing so then I switched they
> keyboard and mouse receivers and then it worked. Everything was
> working fine before shutting down the computer though.
> 

Let's add a few people...
Comment 2 John 2012-06-29 08:38:29 UTC
Created attachment 74421 [details]
As requested by Nestor here is a dmesg file when the issue happened 

This is dmesg since system start to replugging the mouse receiver and getting it back to work.
Comment 3 Roger Davis 2012-08-08 00:51:41 UTC
It seems that there may be a lack of communication.  There are LOTS of these cases.  

Please see   http://ubuntuforums.org/search.php?searchid=87273303
Comment 4 John 2012-08-08 02:03:48 UTC
Created attachment 77091 [details]
logitech fix
Comment 5 John 2012-08-08 02:04:38 UTC
Nestor Lopez Casado from Logitech has already a fix for this issue.
Unfortunately it caused some side problems (latency after not using the mouse for a long time) and was looking to clean up his changeset before sending it upstream.

I have attached the patch he sent me to the bug.

I do not have an ETA unfortunately.
Comment 6 Jay 2012-09-09 21:46:58 UTC
I checked the patch (Comment #4) and it didn't work for me.
Comment 7 Roger Davis 2012-09-10 07:25:50 UTC
Two big points about my situation:
1) I have both a mouse and keyboard that uses the same (unifying) receiver.  This seems to be different from at least some of the above comments.
2) The above attachment is a .bin file.  These can be universal, but I'm not sure if this is for Windows, Linux, or both.  Can someone advise me?
3) Is the above attachment for the "Unifying" receiver, or one-on-one receivers, or???

Thanks!
Comment 8 Roger Davis 2012-09-10 07:31:12 UTC
Also, just to make it clear, I have problems with both Windows pro 7, and Ubuntu 12.04.  I use both operating systems on the same computer.

Problems can be with the mouse and/or the keyboard.

It makes a BIG difference as to which USB port I use.  It seems that the farther I get from the motherboard, the better it works.  The best result (almost ok) is the USB type 2.0 port on a card reader.  My system has up to type 3.0 ports, on which it does NOT work at all well.
Comment 9 Que Quotion 2012-09-18 18:46:30 UTC
Having this problem in Ubuntu 12.04 with upstream kernel 3.5.0-8-generic.

Unloading and reloading the hid_logitech_dj module works, but once in a rare while the receiver will pick up the mouse and ignore the keyboard.

The fastest and surest way I've found to get both mouse and keyboard working is to unplug and replug the usb receiver repeatedly until i see both devices detected by watching kern.log in gnome-system-log.

I do hope there will be a patch before the contacts in my usb port wear thin.
Comment 10 Alan 2012-09-18 18:54:31 UTC
I've fixed one nasty bug in hid_logitech_dj for 3.6. 

https://lkml.org/lkml/2012/8/20/378

You may be hitting that, hard to guess as its a memory scribble type bug. Once 3.6 comes out if you can test it that will be useful.
Comment 11 Giuseppe Dia 2012-09-25 10:18:03 UTC
I am having the same problem too. Some informations:
System: Ubuntu precise 12.04.1 LTS
Kernel: 3.2.0-30.48 (first occurrence)
Comment 12 Giuseppe Dia 2012-09-25 10:48:50 UTC
(..continued, sorry for the hasty commit above)
Architecture:amd64
System: Ubuntu precise 12.04.1 LTS
Kernel in use: 3.6.0-999-generic #201209240405 Mainline tree from http://kernel.ubuntu.com/~kernel-ppa/mainline
Some relevant information
Xorg version is 1:7.6+12ubuntu1
Xorg log: http://pastebin.com/RYfLtTVG
Modules: usbhid,hid,usb_storage
Logitech wired mouse model is M-Bj69 (quite old).
The mouse is not responsive at boot from a cold start. Keyboard USB Logitech K120 works everytime. Problem can be reproduced every cold start with   3.6.0-999.201209240405 and 3.2.0-30.48.
Un/Plugging again the mouse works for me and mouse works fine from then on.
I don't remember any occurrence of this with ubuntu stock 3.2.0-27.43, it started for me upgrading from ubuntu stock 3.2.0-27.43 to 3.2.0-30.48. Mouse works fine with other hardware and on a different i386 system with ubuntu stock 3.0.0
Hope this help to narrow down the issue, if you need further information please feel free to ask.
Comment 13 Jay 2012-10-01 22:30:11 UTC
I can confirm Comment #12. My mouse didn't start from boot (mainline 3.6 2012-09-30), but start work after unplug/plug.
Comment 14 Jiri Kosina 2012-12-03 12:53:15 UTC
Was this really 3.6, or 3.6-rcX?

This should be fixed by

commit 596264082f10dd4a567c43d4526b2f54ac5520bc
Author: Nestor Lopez Casado <nlopezcasad@logitech.com>
Date:   Fri Sep 21 12:21:34 2012 +0200

    HID: Fix logitech-dj: missing Unifying device issue

which went into 3.6-rc7.
Comment 15 Roger Davis 2012-12-07 04:35:57 UTC
Was this really 3.6, or 3.6-rcX?

roger@roger-desktop:~$ uname -a
Linux roger-desktop 3.2.0-34-generic #53-Ubuntu SMP Thu Nov 15 10:48:16 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Will the patch here
-----------------------------
Comment #14 From Jiri Kosina 2012-12-03 12:53:15 (-) [reply]

Was this really 3.6, or 3.6-rcX?

This should be fixed by

commit 596264082f10dd4a567c43d4526b2f54ac5520bc
Author: Nestor Lopez Casado <nlopezcasad@logitech.com>
Date:   Fri Sep 21 12:21:34 2012 +0200

    HID: Fix logitech-dj: missing Unifying device issue

which went into 3.6-rc7.
------------------------------------
work on my system and fix my problem?
Comment 16 John 2012-12-07 05:13:45 UTC
It worked for me.

Thanks!
Comment 17 dino99 2012-12-08 13:01:21 UTC
kernels 3.2 & latest 3.7 are also affected
Comment 18 Roger Davis 2012-12-09 09:42:20 UTC
Sounds good to me except how do I implement this in Ubuntu 12.04 ?

Thanks!
Comment 19 Jay 2013-07-01 21:37:03 UTC
Regression in 3.10. Mouse don't work at all. In 3.9 works.

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