You are not logged in.
Hi,
I'm running an up-to-date arch linux (kernel 3.17.3) on a Thinkpad T440s.
after a while (minutes to hours) my external keyboard (lenovo compact usb)
stops working, and all other USB devices I attempt to use afterwards are
not recognized either (sticks, mouse, ...).
The only things in my log file for the period when it happens:
Nov 23 06:57:13 lambda slim[1714]: ATTENTION: default value of option force_s3tc_enable overridden by environment.
Nov 23 06:57:32 lambda slim[1714]: [WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
Nov 23 06:59:23 lambda kernel: pci_pm_runtime_suspend(): hcd_pci_runtime_suspend+0x0/0x60 [usbcore] returns -16
Nov 23 07:00:33 lambda slim[1714]: [ERROR:flash/platform/pepper/pep_keyboard.cpp(143)] NOTREACHED() reached
Nov 23 07:00:35 lambda slim[1714]: [ERROR:flash/platform/pepper/pep_keyboard.cpp(143)] NOTREACHED() reached
Nov 23 07:01:01 lambda crond[20215]: pam_unix(crond:session): session opened for user root by (uid=0)
My search engine of choice didn't bring up any relevant matches. The pepper
messages come from the chromium flash plugin.
I haven't used the keyboard regularly, so I don't know if that behavior is new.
I've no idea what to try... any suggestions?
thanks in advance
Edit: attempted to disconnect keyboard, suspend / resume / reconnect keyboard, and it's back!
The problem seems to be related to suspend / powersave features. Note that the keyboard stopped working in the middle of me typing, and not directly after resume, though.
Last edited by dispanser (2014-11-26 10:27:42)
Offline
Nov 23 06:59:23 lambda kernel: pci_pm_runtime_suspend(): hcd_pci_runtime_suspend+0x0/0x60 [usbcore] returns -16
Definitely a power management problem. You might find some clue here
do it good first, it will be faster than do it twice the saint ![]()
Offline
thanks, the link was spot on.
for future reference:
I blacklisted the device from usb suspend mode by editing to contain /etc/laptop-mode/conf.d/runtime-pm.conf
AUTOSUSPEND_RUNTIME_DEVID_BLACKLIST="17ef:6047"
I figured the device ID out by looking at the output of lsusb -v
Offline