Your message dated Mon, 13 Jun 2016 14:16:14 +0530
with message-id <[email protected]>
and subject line Re: Bug#809852: laptop-mode-tools: usb mouse freeze due to
power management config
has caused the Debian Bug report #809852,
regarding add debconf interface about flaky drivers
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 [email protected]
immediately.)
--
809852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809852
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: laptop-mode-tools
Version: 1.68-3
Severity: important
Tags: patch
Dear Maintainer,
laptop-mode-tools is creating a weird bug for usb mouse. After installing
laptop-mode-tools and rebooting my laptop, I found that my usb mouse (wired and
wireless tested) will be disable after few second of idle.
I have to click the mouse button several times in order to activate it back,
and it will be disabled again in few seconds.
Searching the Internet was proven very hard to find the solution, but I manage
to found out the root cause from one of the posting on Internet.
It turns out that laptop-mode-tools is aggressively disabling usb port in order
to save power, thus disabling usb mouse in the process.
The solution to the issue by blacklisting usbhid and psmouse kernel module,
restarting laptop-mode-tool, and then replugging my usb mouse.
No issue after that.
Because usb mouse is quite common, I believe usbhid kernel module should be
blacklisted by default. Failure to blacklist the module will cause unneeded
troubleshooting and people will blame linux desktop is not ready for major
usage.
I believe a lot of other usb related bug such as wifi disabled, bluetooth
disabled, etc, was caused by this agressive power management for usb ports.
Please see my config file attached, and apply it to the default config.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 4.3.0-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages laptop-mode-tools depends on:
ii init-system-helpers 1.24
ii lsb-base 9.20150917
ii psmisc 22.21-2.1
ii util-linux 2.27.1-1
Versions of packages laptop-mode-tools recommends:
pn ethtool <none>
ii hdparm 9.43-2
ii net-tools 1.60+git20150829.73cef8a-2
pn python-qt4 <none>
pn sdparm <none>
ii udev 228-2+b1
ii wireless-tools 30~pre9-8
Versions of packages laptop-mode-tools suggests:
ii acpid 1:2.0.25-1
-- Configuration Files:
/etc/laptop-mode/conf.d/runtime-pm.conf changed:
DEBUG=0
CONTROL_RUNTIME_AUTOSUSPEND=1
AUTOSUSPEND_USE_WHITELIST=0
AUTOSUSPEND_RUNTIME_DEVID_BLACKLIST=""
AUTOSUSPEND_RUNTIME_DEVTYPE_BLACKLIST="usbhid psmouse"
AUTOSUSPEND_RUNTIME_DEVID_WHITELIST=""
AUTOSUSPEND_RUNTIME_DEVTYPE_WHITELIST=""
BATT_SUSPEND_RUNTIME=1
LM_AC_SUSPEND_RUNTIME=1
NOLM_AC_SUSPEND_RUNTIME=1
AUTOSUSPEND_TIMEOUT=2
-- no debconf information
--- runtime-pm.conf.orig 2016-01-05 01:10:27.413802611 +0800
+++ runtime-pm.conf 2016-01-04 01:34:02.893158179 +0800
@@ -42,7 +42,7 @@
# The list of device driver types that should not use autosuspend. The driver
# type is given by "DRIVER=..." in a device's uevent file.
# Example: AUTOSUSPEND_DEVID_BLACKLIST="usbhid usb-storage"
-AUTOSUSPEND_RUNTIME_DEVTYPE_BLACKLIST=""
+AUTOSUSPEND_RUNTIME_DEVTYPE_BLACKLIST="usbhid psmouse"
# The list of Device IDs that should use autosuspend. Use system commands or
# look into sysfs to find out the IDs of your devices.
--- End Message ---
--- Begin Message ---
Control: fixed -1 1.69-2
In 1.69, the default list now blacklists devices of USB Device type HID, Storage
and Hub. With this default list, the usual USB Mouse/Keyboard issues are
reported to have been fixed.
As for the Debconf prompt, I dropped that thought because many derivatives
prefer a promptless workflow.
I am closing this bug report. But if you still see the problem, please feel free
to re-open.
Thanks,
Ritesh
On Mon, 2016-01-04 at 18:58 +0100, Ritesh Raj Sarraf wrote:
> Thank you for the bug report. This behavior is already known and a
> tricky one.
>
> The thing is, it is the device drivers that are at fault here. But I do
> agree that the overall experience of a Linux Desktop takes the beating.
>
> To counter this, Laptop Mode Tools provides multiple options of
> blacklisting devices. Not just the USB family driver driver modules,
> you can hand pick your (faulty) USB devices and blacklist them.
>
> This has been documented in README.Debian. Blacklisting generic device
> driver modules would mean we conserve less power, something I'm not a
> fan of. That is the sole reason for adding the "blacklist by device id"
> option.
>
> This is a common problem in Linux too. If you look at the Linux
> kernel's source, there are 100s of devices that have quirks defined.
>
> Blacklisting a device family is not the best idea. The best approach
> would be to provide a Debconf prompt and educate the user about it.
>
> But then there is the problem for derivatives that completely avoid the
> debconf prompt (for good reasons). For them too, Laptop Mode Tools
> provides an overriding option. And ofcourse, they can always carry a
> patch modifying the defaults.
>
>
> I think, for Debian, the best is to add an explicit Debconf prompt.
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
signature.asc
Description: This is a digitally signed message part
--- End Message ---
