From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: "Dâniel Fraga" <fragabr@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: 3.5.1 hid_generic causes mouse locking until a button is clicked
Date: Sun, 12 Aug 2012 19:53:29 +0200 [thread overview]
Message-ID: <20120812195329.2cb454c3@neptune.home> (raw)
In-Reply-To: <k06dcc$u9q$1@dough.gmane.org>
Hi,
On Sat, 11 August 2012 Dâniel Fraga <fragabr@gmail.com> wrote:
> I upgraded from 3.4.4 to 3.5.1 kernel and now I see the new
> hid_generic module is causing problem with my mouse (a regular Logitech
> USB optical mouse).
>
> The problem is: after 2 seconds without moving the mouse, the
> pointer will NOT move again UNLESS I click a mouse button.
>
> So now I have to click a button everytime I want to "unlock"
> the mouse pointer. It didn't happen with 3.4.4 so it's clearly a
> regression.
>
> Any hints? I can try patches. Thanks.
This might be USB-autosuspend. 2 seconds seems to match the default
delay for autosuspending USB devices.
Have a look at the values under /power/ for your USB devices.
(probably the port to which your mouse is connected and/or the mouse
itself).
Check if disabling USB-autosuspend helps.
Compare the output of:
grep . /sys/bus/usb/devices/*/power/*
for the time your mouse can move your pointer and when it can't.
Also change the autosuspend delay or disable autosuspend for the
mouse.
See also in your kernel sources:
Documentation/usb/power-management.txt
Documentation/ABI/testing/sysfs-bus-usb
Bruno
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-08-12 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-11 19:55 3.5.1 hid_generic causes mouse locking until a button is clicked Dâniel Fraga
2012-08-12 17:53 ` Bruno Prémont [this message]
2012-08-12 21:16 ` Dâniel Fraga
2012-08-13 6:30 ` Oliver Neukum
2012-08-13 9:18 ` Dâniel Fraga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120812195329.2cb454c3@neptune.home \
--to=bonbons@linux-vserver.org \
--cc=fragabr@gmail.com \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).