On Tue, Nov 14, 2017 at 7:49 AM, Justin Forbes <jmforbes@xxxxxxxxxxx> wrote: > On Mon, Nov 13, 2017 at 10:16 AM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: >> Some tips on how regressions might manifest and what information to >> include in a good bug report would be useful. e.g. on an Intel NUC >> when I run powertop --auto-tune, and walk away (it's a server so it >> might be days) and come back the keyboard won't work. I've never done >> any troubleshooting other than just disable the powertop systemd unit, >> I'm vaguely suspicious of usb autosuspend and it not waking up when >> keys are pressed. >> > > Auto suspend can be a real problem when it is keyboards and mice. I > know there was a huge uproar with logitech unified receiver users when > powertop would change the receiver to autosuspend and the > keyboard/mouse became unresponsive for a couple of key presses. To be > honest, I think this particular change may do much more harm than > good. > I find it ironic that this misbehaving hardware is Intel's USB stuff, in their NUC, and powertop is an Intel managed project. I'd guess the powertop folks would already know better than to apply autosuspend to Intel USB hardware. -- Chris Murphy _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx
