FS#15234 - [kernel26] Mouse is off after few seconds

Attached to Project: Arch Linux
Opened by Mateusz Tracz (matiit) - Tuesday, 23 June 2009, 17:21 GMT
Last edited by Jan de Groot (JGC) - Sunday, 28 June 2009, 21:22 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan de Groot (JGC)
Thomas Bächler (brain0)
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
When I've updated kernel to 2.6.30-5 and rebooted laptop, my mouse is working, but if I don't use it for 5seconds it is turning off, i must to click for it is working properly. It is very inconvenient.
On last .29 kernel, everything is great. Dmesg shows nothing.

Additional info:
* package version(s) - kernel26-2.6.30-5
* config and/or log files etc.


Steps to reproduce:
Boot up system with kernel-2.6.30, leave mouse alone and wait five seconds.
This task depends upon

Closed by  Jan de Groot (JGC)
Sunday, 28 June 2009, 21:22 GMT
Reason for closing:  Not a bug
Additional comments about closing:  http://lkml.org/lkml/2009/4/9/457

Check the discussion. 2.6.29 didn't do what it was told to do.
Comment by Ramses de Norre (Ramses_de_Norre) - Tuesday, 23 June 2009, 17:46 GMT
I can confirm this, every time I leave my mouse to rest for a few seconds I have to click it to activate it again. This is extremely annoying and counter-productive.
Comment by Mateusz Tracz (matiit) - Tuesday, 23 June 2009, 17:49 GMT
And one thing. If i plug off and plug on mouse there is no problem...
Comment by Thomas Bächler (brain0) - Tuesday, 23 June 2009, 18:14 GMT
I'm just guessing here: Is USB autosuspend enabled? (cat /sys/module/usbcore/parameters/autosuspend) You can disable autosuspend for specific devices if you want to. I don't have other ideas right now.
Comment by Mateusz Tracz (matiit) - Tuesday, 23 June 2009, 18:18 GMT
i've been trying turn off autosuspend..it didn't help..
It is not this.
Comment by Ramses de Norre (Ramses_de_Norre) - Tuesday, 23 June 2009, 20:08 GMT
Autosuspend is not the culprit here neither. By the way, my touchpad doesn't seem to be affected, only the usb mouse.
Comment by Mateusz Tracz (matiit) - Tuesday, 23 June 2009, 20:10 GMT
My touchpad neither. I will compile today own kernel and check is it a configuration issue.
Comment by Thomas Bächler (brain0) - Tuesday, 23 June 2009, 20:59 GMT
I've mostly used my touchpad and my bluetooth mouse recently. I just connected my old Logitech USB mouse and I cannot reproduce the problem. That said, only more info will help - if you can tell me enough to reproduce it then I may be able to do something.
Comment by Mateusz Tracz (matiit) - Tuesday, 23 June 2009, 21:02 GMT

if i want to reproduce i must to boot with mouse plug on... not plug it after boot

Comment by Ramses de Norre (Ramses_de_Norre) - Tuesday, 23 June 2009, 21:12 GMT
If I plug and unplug the mouse, the problem seems to be gone. (Relieves the inconvenience a bit, I don't know whether it returns on specific occasions)

I can provide all info you want but I don't really know where to start, I'll attach everything.log and my xorg log, you can ask if you need other log files.
Comment by Aaron Griffin (phrakture) - Tuesday, 23 June 2009, 21:12 GMT
Questions to try to diagnose this:
* Are these wireless or wired mice?
* Are you using evdev?
* Are you using hal?
Comment by Ramses de Norre (Ramses_de_Norre) - Tuesday, 23 June 2009, 21:17 GMT
* Wired mouse
* Using evdev
* Hal hotplugging enabled, I haven't altered any fdi files for my mouse.
Comment by Jan de Groot (JGC) - Tuesday, 23 June 2009, 23:02 GMT
It looks like X goes into standby now and then. I see multiple entries of connections to the acpid socket, a memory layout for your videocard and the re-opening of all input devices including keyboard. Is this Xorg.0.log from a session with suspending, or is it just one run where you lose the keyboard now and then?
Comment by Mateusz Tracz (matiit) - Wednesday, 24 June 2009, 07:24 GMT
I have cable optical mouse
I use evdev
Use hal hotplugging
Comment by Greg (dolby) - Wednesday, 24 June 2009, 08:01 GMT
Works great here with xf86-input-mouse and a xorg-server without input hotplugging. Both touchpad and USB connected Microsoft mouse
Comment by Mateusz Tracz (matiit) - Wednesday, 24 June 2009, 08:11 GMT
But it is in 100% kernel26 fault. On .29 works great.
Comment by Thomas Bächler (brain0) - Wednesday, 24 June 2009, 08:28 GMT
Here is what we need (the everything.log from above is just too much):

1) Boot with the mouse connected (that's where you said it fails)

- Save dmesg
- Save Xorg.0.log
- Disconnect the mouse and connect it (you said it should work now)
- Save dmesg again
- Save Xorg.0.log again

Diff the saved dmesg and Xorg.0.log and mark the place where you disconnected the mouse. That will help us analyze what happens when re-plugging the mouse.

2) Boot with the mouse disconnected, connect it later (that's where you said it works)

- Save dmesg
- Save Xorg.0.log

I hope that from this data we can find the problem, but there is obviously no guarantee.
Comment by Mateusz Tracz (matiit) - Wednesday, 24 June 2009, 09:00 GMT
dmesg_fail.log - dmesg after boot, kernel has already turned off mouse, just click to turn on
dmesg_good.log - dmesg after replugging mouse
dmesg_diff.log - diff of dmesg_fail and dmesg_goog
I will attach in a moment dmesg when i plug mouse after boot.
Xorg.0.log is unneeded because i have no DisplayManager and mouse is turning off when X aren't started too
Comment by Mateusz Tracz (matiit) - Wednesday, 24 June 2009, 09:04 GMT
dmesg_plug_after_boot.log - log when plugging mouse after boot (then mouse isn't turning off)
Comment by Ramses de Norre (Ramses_de_Norre) - Wednesday, 24 June 2009, 10:08 GMT
@JCG: I suspend and hibernate my laptop a lot, so those stanby entries are probably caused thereby.

I'll do what you asked about the log files tomorrow, I have my final exam in two hours so I don't have time left today.
Comment by Tom (reztho) - Wednesday, 24 June 2009, 13:37 GMT
It happened here too.

I fixed it by preventing the laptop_mode daemon from controlling the usb autosuspend. You should reboot when you do the change.

File: /etc/laptop-mode/conf.d/usb-autosuspend.conf
CONTROL_USB_AUTOSUSPEND to 0
Comment by Mateusz Tracz (matiit) - Thursday, 25 June 2009, 11:02 GMT
I've compiled my own kernel so i don't know is CONTROL_USB_AUTOSUSPEND to 0 solving a problem for me, but i'm guessing - yes, cause of i had it set to 1
Comment by Aaron Griffin (phrakture) - Friday, 26 June 2009, 17:59 GMT
Is this caused by USB autosuspend for everyone?
Comment by Thomas Bächler (brain0) - Friday, 26 June 2009, 18:06 GMT
Just curious, I didn't find that option anywhere in the kernel config. Also, USB autosuspend is disabled by default if I am correct.
Comment by Ramses de Norre (Ramses_de_Norre) - Friday, 26 June 2009, 18:30 GMT
Sorry for my late response, I haven't had any problems since I rebooted after disabling usb autosuspend. It seems like it was caused by usb autosuspend and that a reboot was necessary. Strange though, previous kernels didn't suspend a port that was being used.

Loading...