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

[Mario.Limonciello]

> -----Original Message-----
> From: Paul Menzel <pmenzel@xxxxxxxxxxxxx>
> Sent: Monday, November 4, 2019 10:11 AM
> To: Limonciello, Mario; Mika Westerberg
> Cc: Andreas Noever; Michael Jamet; Yehezkel Bernat; Christian Kellner; linux-
> kernel@xxxxxxxxxxxxxxx; Anthony Wong
> Subject: Re: USB devices on Dell TB16 dock stop working after resuming
> 
> Dear Mika, dear Mario,
> 
> 
> On 2019-11-04 16:49, Mario.Limonciello@xxxxxxxx wrote:
> 
> >> From: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
> >> 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?

> 
> >>> 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.