Re: USB devices on Dell TB16 dock stop working after resuming

From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Mario Limonciello <mario.limonciello@dell.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Andreas Noever <andreas.noever@gmail.com>,
	Michael Jamet <michael.jamet@intel.com>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	Christian Kellner <ck@xatom.net>,
	linux-kernel@vger.kernel.org,
	Anthony Wong <anthony.wong@canonical.com>
Subject: Re: USB devices on Dell TB16 dock stop working after resuming
Date: Mon, 4 Nov 2019 17:22:55 +0100	[thread overview]
Message-ID: <848469e4-b084-5d19-91cc-e4a7f914d0b3@molgen.mpg.de> (raw)
In-Reply-To: <fef12597547e475cb240a0bb6c1c2ed7@AUSX13MPC105.AMER.DELL.COM>

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

Dear Mario,

On 2019-11-04 17:17, Mario.Limonciello@dell.com wrote:

>> From: Paul Menzel <pmenzel@molgen.mpg.de>
>> Sent: Monday, November 4, 2019 10:11 AM

>> On 2019-11-04 16:49, Mario.Limonciello@dell.com wrote:
>>
>>>> From: Mika Westerberg <mika.westerberg@linux.intel.com>
>>>> Sent: Monday, November 4, 2019 9:45 AM
>>
>>>> On Mon, Nov 04, 2019 at 04:44:40PM +0200, Mika Westerberg wrote:
>>>>> On Mon, Nov 04, 2019 at 04:25:03PM +0200, Mika Westerberg wrote:
>>
>>>>>> On Mon, Nov 04, 2019 at 02:13:13PM +0100, Paul Menzel wrote:
>>
>>>>>>> On the Dell XPS 13 9380 with Debian Sid/unstable with Linux 5.3.7
>>>>>>> suspending the system, and resuming with Dell’s Thunderbolt TB16
>>>>>>> dock connected, the USB input devices, keyboard and mouse,
>>>>>>> connected to the TB16 stop working. They work for a few seconds
>>>>>>> (mouse cursor can be moved), but then stop working. The laptop
>>>>>>> keyboard and touchpad still works fine. All firmware is up-to-date
>>>>>>> according to `fwupdmgr`.
>>>>>>
>>>>>> What are the exact steps to reproduce? Just "echo mem >
>>>>>> /sys/power/state" and then resume by pressing power button?
>>
>> GNOME Shell 3.34.1+git20191024-1 is used, and the user just closes the
>> display. So more than `echo mem > /sys/power/state` is done. What
>> distribution do you use?
> 
> I guess this is then using systemctl's sleep command and anything it does as a
> result?
> 
> IIRC that has support for doing extra stuff if you want to via scripts.
> Any extra scripts you've put in place?  Or your distro is running?

Debian Sid/unstable configuration is used with no custom changes. I’ll check
tomorrow, if it’s reproducible with `echo mem | sudo too /sys/power/state`.

>>>>> I tried v5.4-rc6 on my 9380 with TB16 dock connected and did a couple of
>>>>> suspend/resume cycles (to s2idle) but I don't see any issues.
>>>>>
>>>>> I may have older/different firmware than you, though.
>>>>
>>>> Upgraded BIOS to 1.8.0 and TBT NVM to v44 but still can't reproduce this
>>>> on my system :/
>>
>> The user reported the issue with the previous firmwares 1.x and TBT NVM v40.
>> Updating to the recent version (I got the logs with) did not fix the issue.
>>
>>> Loop Anthony.  Anthony can you see if you guys repro this at all too?
>>>
>>> As a potential point of comparison and sometimes pain area, I'm wondering if
>>> something in userland is poking power states for Paul leading to this.
>>>
>>> Paul what sort of power management policies are you using on your machine?
>>> Anything like:
>>> * powertop  --auto-tune,
>>> * TLP
>>> * systemd > 243 (contains some stuff for automatic suspend)
>>
>> I’ll check with the user again, but to my knowledge nothing from the list is
>> used on the device.
> 
> Those are just illustrative examples, anything else that you're doing
> above and beyond "stock" Debian unstable would be useful to note too
> in this area.

Sorry for being unclear. No customizations were done.

Kind regards,

Paul

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]