Re: [Powertop] RH Bugzilla [Bug 1482649] Logitech USB Unified Receiver+M570 need 'waking' up by click after kernel update

Re: [Powertop] RH Bugzilla [Bug 1482649] Logitech USB Unified Receiver+M570 need 'waking' up by click after kernel update

[Joe Konno]

[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]

On Thu, 7 Sep 2017 18:09:59 +0000
Mike Simms <micsim2007(a)outlook.com> wrote:

> Then explain why it was never an issue before kernel 4.12 please

That's a question for the maintainer of the kernel USB HID driver driver
community. The Linux kernel is a very large piece of software with many, many
device drivers supporting still more devices. These drivers can and do change,
for myriad reasons, from kernel release to kernel release.

Particular device power management behaviors are implemented by kernel device
drivers. PowerTOP gives you the ability to toggle (or tune) low-level,
power-sensitive settings for each device. If by toggling a setting for a
particular device that device behaves in an undesirable way, you may have a
kernel device driver bug.

USB HID-- human interface device-- drivers, which include mice and the like,
have an upstream kernel maintainer. In this specific case, the linux-usb
mailing list would be a good starting point, or the kernel.org bugzilla.

In the general case, consulting the kernel MAINTAINERS file for the device in
question should provide a mailing list starting point when issues like these
arise.

Here I can only offer general advice, nothing specific. Hope it helps!

[-- Attachment #2: attachment.sig --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [Powertop] RH Bugzilla [Bug 1482649] Logitech USB Unified Receiver+M570 need 'waking' up by click after kernel update

[Mike Simms]

[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]

Out of courtesy, just a quick message thank you for your help
and pointing me in the right direction with this issue. I'm closing it
after further consultation with linux-usb contributors. Here is the
reason copied from my RH Bugzilla submission:

I've been collaborating the last 6 days with powertop and linux-usb
contributors upstream over this issue. They have been very helpful.
What we've managed to do is establish exactly what has changed and
where using a number of different trace methods.

There's basically not a bug as such, it is a setting that has been
fixed in 4.12 and above that never worked before.

The value for power stored in
the /sys/bus/usb/devices/2.1.3/power/control file for this device was
being ignored when set to auto (Good) by powertop with kernel 4.11 and
instead a non-existent setting of ON is used. ON means no autosuspend
as power saving is 'Bad' in powertop tunable terms.

with 4.12 it is not being ignored. So what I'm going to do now is
investigate masking that setting with powertop by removing it as a
system service and coding a script (found something similar done for
another distribution so I'm going to at least try it) to autostart
powertop at boot ignoring the pointing device. OR using something else
like tlp which I have no experience with. Either way, this is clearly
not a bug after further investigation upstream so I'm closing it. I
will post the powertop solution if I can get it worked but this should
remain closed from here on in.

Re: [Powertop] RH Bugzilla [Bug 1482649] Logitech USB Unified Receiver+M570 need 'waking' up by click after kernel update

[Mike Simms]

[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]

Auke, no that autotune has always been set to good. It's been discussed
already in the RH bug thread I linked to in my 1st post here. I didn't
want to duplicate everything already gone through because it's quite
lengthy. I'm asking here in case someone has any better suggestions
because it should still work the same in theory. No settings have been
changed in powertop. It autodetects and sets good for both kernel
versions with regards the Logitech unified receiver.

To summarise for people who don't want to read the RH bugzilla thread:

Autotune service for both kernels tunes the same devices to Good.
Nothing is set to Bad.

With kernel 4.11.11-300 there is no wake up lag when the receiver and
connected device has entered low power state

With kernel 4.12.x and 4.13 release candidate there is lag you can
measure in seconds and it's extremely frustrating. It causes missed
clicks, keyboard characters,  duplicate form submissions on websites.

Setting the autosuspend for the receiver to Bad is an obvious
workaround but it isn't the solution we're looking for. There is a
regression here that needs addressing. Hopefully the HID driver contact
I found thanks to Joe will be able to advise further on this.

Re: [Powertop] RH Bugzilla [Bug 1482649] Logitech USB Unified Receiver+M570 need 'waking' up by click after kernel update

[Mike Simms]

[-- Attachment #1: Type: text/plain, Size: 198 bytes --]

Thanks Joe, I've found an email address for a Jiri Kosina who maintains
the HID driver for linux-usb if their site list is up to date. I've
tried emailing them and will see what comes of it now.

[-- Attachment #2: attachment.mht --]
[-- Type: message/rfc822, Size: 52 bytes --]



WzxlbWFpbC5tZXNzYWdlLk1lc3NhZ2UgaW5zdGFuY2UgYXQgMHg3ZmRiOGEyODViZDg+XQ==

Re: [Powertop] RH Bugzilla [Bug 1482649] Logitech USB Unified Receiver+M570 need 'waking' up by click after kernel update

[Auke Kok]

[-- Attachment #1: Type: text/plain, Size: 768 bytes --]

On 09/07/2017 11:09 AM, Mike Simms wrote:
> Then explain why it was never an issue before kernel 4.12 please

I can only take a guess, based on the info you provided, most
importantly I lack the hardware that you have.

Joe's comments are obviously important - there may be several points of
failure. The one that I spotted, is this one:

>>> powertop is using the autotune profile and the usb autosuspend
>>> entry is Good.

Turn it to "Bad" and see if it resolves the problem.

I am wondering if powertop autotuning was recently turned on in your
distro, and the trackpoint isn't properly blacklisted as a device that
shouldn't be put into usb autosuspend (if that is actually a thing in
code, it's been a while since I last worked on it).

Auke

Re: [Powertop] RH Bugzilla [Bug 1482649] Logitech USB Unified Receiver+M570 need 'waking' up by click after kernel update

[Mike Simms]

[-- Attachment #1: Type: text/plain, Size: 2598 bytes --]

Then explain why it was never an issue before kernel 4.12 please

On Thu, 7 Sep 2017 10:30:34 -0700
Auke Kok <auke-jan.h.kok(a)intel.com> wrote:

> 
> This is indicative of enabling usb suspend for the trackball device,
> and common to mice, touchpads and trackballs.
> 
> The only solution is to disable usb suspend for these devices, and
> remember not to enable it for the device in powertop.
> 
> Auke
> 
> 
> 
> On 09/07/2017 06:32 AM, Mike Simms wrote:
> > Description of problem: For some reason the trackball is no longer
> > able to respond to user input immediately. it only responds when I
> > click a button to wake it up or roll the ball about a bit first.
> > With earlier kernels this was not necessary. Booting from the
> > previous kernel 4.11.11-300.fc26 and it still works fine.
> > 
> > 
> > Version-Release number of selected component (if
> > applicable):4.12.5-300.fc26.x86_64
> > 
> > Also affected Fedora 27 4.13 rc kernel
> > 
> > 
> > How reproducible: consistently
> > 
> > 
> > Steps to Reproduce:
> > 1. start notebook computer with the unified receiver attached
> > 2. login and use the computer as normal
> > 
> > Actual results: trackball works initially but if left for a few
> > seconds to type or read for example, it needs waking up with
> > movement or a click of a button.
> > 
> > 
> > Expected results: should respond normally without this lag or
> > waking up nonsense
> > 
> > 
> > Additional info:the unified receiver is plugged into the same USB 2
> > port it has always been.
> > 
> > powertop is using the autotune profile and the usb autosuspend
> > entry is Good.
> > 
> > Something in the kernel code has caused a power management
> > regression. I'm not sure what and the bug I opened so far has drawn
> > a blank. The kernel maintainer is not able to help as they don't
> > know about power management or powertop. please give some guidance
> > as to where to look and how to resolve this if possible. Full
> > information so far here, including dmesg, lspci, lsusb output,
> > dumps for comparison of power profiles etc.
> > 
> > I'm an end user, not a developer or maintainer so please keep it in
> > relatively simple terms I can relay back to the maintainers please
> > and understand at the same time.
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=1482649
> > 
> > Thanks
> > 
> > Mike Simms
> > _______________________________________________
> > PowerTop mailing list
> > PowerTop(a)lists.01.org
> > https://lists.01.org/mailman/listinfo/powertop
> > 
> 

Re: [Powertop] RH Bugzilla [Bug 1482649] Logitech USB Unified Receiver+M570 need 'waking' up by click after kernel update

[Auke Kok]

[-- Attachment #1: Type: text/plain, Size: 2305 bytes --]


This is indicative of enabling usb suspend for the trackball device, and
common to mice, touchpads and trackballs.

The only solution is to disable usb suspend for these devices, and
remember not to enable it for the device in powertop.

Auke



On 09/07/2017 06:32 AM, Mike Simms wrote:
> Description of problem: For some reason the trackball is no longer able
> to respond to user input immediately. it only responds when I click a
> button to wake it up or roll the ball about a bit first. With earlier
> kernels this was not necessary. Booting from the previous kernel
> 4.11.11-300.fc26 and it still works fine.
> 
> 
> Version-Release number of selected component (if
> applicable):4.12.5-300.fc26.x86_64
> 
> Also affected Fedora 27 4.13 rc kernel
> 
> 
> How reproducible: consistently
> 
> 
> Steps to Reproduce:
> 1. start notebook computer with the unified receiver attached
> 2. login and use the computer as normal
> 
> Actual results: trackball works initially but if left for a few seconds
> to type or read for example, it needs waking up with movement or a
> click of a button.
> 
> 
> Expected results: should respond normally without this lag or waking up
> nonsense
> 
> 
> Additional info:the unified receiver is plugged into the same USB 2
> port it has always been.
> 
> powertop is using the autotune profile and the usb autosuspend entry is
> Good.
> 
> Something in the kernel code has caused a power management regression.
> I'm not sure what and the bug I opened so far has drawn a blank. The
> kernel maintainer is not able to help as they don't know about power
> management or powertop. please give some guidance as to where to look
> and how to resolve this if possible. Full information so far here,
> including dmesg, lspci, lsusb output, dumps for comparison of power
> profiles etc.
> 
> I'm an end user, not a developer or maintainer so please keep it in
> relatively simple terms I can relay back to the maintainers please and
> understand at the same time.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1482649
> 
> Thanks
> 
> Mike Simms
> _______________________________________________
> PowerTop mailing list
> PowerTop(a)lists.01.org
> https://lists.01.org/mailman/listinfo/powertop
> 

[Powertop] RH Bugzilla [Bug 1482649] Logitech USB Unified Receiver+M570 need 'waking' up by click after kernel update

[Mike Simms]

[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]

Description of problem: For some reason the trackball is no longer able
to respond to user input immediately. it only responds when I click a
button to wake it up or roll the ball about a bit first. With earlier
kernels this was not necessary. Booting from the previous kernel
4.11.11-300.fc26 and it still works fine.


Version-Release number of selected component (if
applicable):4.12.5-300.fc26.x86_64

Also affected Fedora 27 4.13 rc kernel


How reproducible: consistently


Steps to Reproduce:
1. start notebook computer with the unified receiver attached
2. login and use the computer as normal

Actual results: trackball works initially but if left for a few seconds
to type or read for example, it needs waking up with movement or a
click of a button.


Expected results: should respond normally without this lag or waking up
nonsense


Additional info:the unified receiver is plugged into the same USB 2
port it has always been.

powertop is using the autotune profile and the usb autosuspend entry is
Good.

Something in the kernel code has caused a power management regression.
I'm not sure what and the bug I opened so far has drawn a blank. The
kernel maintainer is not able to help as they don't know about power
management or powertop. please give some guidance as to where to look
and how to resolve this if possible. Full information so far here,
including dmesg, lspci, lsusb output, dumps for comparison of power
profiles etc.

I'm an end user, not a developer or maintainer so please keep it in
relatively simple terms I can relay back to the maintainers please and
understand at the same time.

https://bugzilla.redhat.com/show_bug.cgi?id=1482649

Thanks

Mike Simms