[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#790398: marked as done (USB keyboard/mouse are aggressively autosuspended, dropping events)

Your message dated Sat, 08 May 2021 12:24:31 -0700 (PDT)
with message-id <6096e56f.1c69fb81.e9a48.1d8c@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #790398,
regarding USB keyboard/mouse are aggressively autosuspended, dropping events
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
790398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790398
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-3.16.0-4-amd64
Version: 3.16.7-ckt11-1

After installing updates today and rebooting, I found that my USB keyboard and mouse, after being idle for exactly two seconds, would be suspended, such that they would not wake up until after a key/button press, and the wake-up press would itself not be reported to software. For the keyboard, this has the effect that the first keystroke or two after being idle would be dropped. For the mouse, the effect is that after being idle, the mouse could no longer move, because movement events would not "wake" it; instead, clicking a button was necessary, after which the mouse would wake up and move normally.

Disabling USB autosuspend fixes the problem. That is:

    echo -1 > /sys/module/usbcore/parameters/autosuspend

Then unplug/replug the USB hub to which both devices are attached.

Before disabling as above, the autosuspend value was 2 (presumably meaning 2 seconds?). I verified that setting it back to 2 (and unplugging/re-plugging the devices again) caused the problem to return.

The affected system is a self-assembled desktop with keyboard and mouse connected through a generic USB hub to USB 2.x ports. Please let me know what specific information would be useful for debugging.

-Kenton

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: