linux-kernel - Re: i8042 AUX port [serio1] suspend takes a second on Dell XPS 13 9360 and TUXEDO Book 1406

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5d6a4804-d4d1-df4f-6b63-43ac6b00af96@molgen.mpg.de>
Date:   Sat, 3 Feb 2018 12:09:44 +0100
From:   Paul Menzel <pmenzel+linux-input@...gen.mpg.de>
To:     Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:     linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
        it+linux-input@...gen.mpg.de
Subject: Re: i8042 AUX port [serio1] suspend takes a second on Dell XPS 13
 9360 and TUXEDO Book 1406

Dear Dmitry,


Am 30.01.2018 um 19:39 schrieb Paul Menzel:

> On 01/30/18 19:07, Dmitry Torokhov wrote:
>> On Tue, Jan 30, 2018 at 09:52:45AM -0800, Dmitry Torokhov wrote:

>>> On Tue, Jan 30, 2018 at 06:36:34PM +0100, Paul Menzel wrote:

>>>> I do not know, when it started, but with Linux 4.14-rc8 and 4.15,
>>>> benchmarking suspend and resume time with `sleepgraph.py` [1][2], 
>>>> there is a
>>>> regression, that i8042 AUX port [serio1] suspend takes a second on 
>>>> Dell XPS
>>>> 13 9360 and TUXEDO Book 1406.
>>>
>>> It would be really helpful to know when the regression started.
>>
>> So the reason it takes longer is because the touchpad does not want to
>> talk to us for some reason and we wait until commands time out:
>>
>> [   94.591636] calling  serio1+ @ 2299, parent: i8042
>> [   94.794292] psmouse serio1: Failed to disable mouse on isa0060/serio1
>> [   95.593303] call serio1+ returned 0 after 974280 usecs
>>
>> but it is not clear why it happens, I do not think we changed anything
>> in that path for a while, so it might be some other change affecting
>> things indirectly. I'm afraid you'll have to narrow the scope, and
>> ideally bisect.
> 
> Thank you for looking into this. Just to note, that it worked with Linux 
> 4.14.1 from Ubuntu 17.10, so it’s probably something in 4.15. Bisecting 
> will take a bit, as the FTRACE stuff broke in Linux 4.15-rc1 and was 
> only fixed in 4.15-rc9. Hopefully, it’s just one commit I need to 
> backport. I’ll get back to you hopefully at the end of the week.

Unfortunately, I am unable to reproduce it currently. Also not with the 
original Linux kernel versions I tried. I’ll report back, when I see it 
the next time.


Kind regards,

Paul