lkml.org 
[lkml]   [2019]   [Nov]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: USB devices on Dell TB16 dock stop working after resuming
Date
> -----Original Message-----
> From: Mika Westerberg <mika.westerberg@linux.intel.com>
> Sent: Wednesday, November 20, 2019 4:51 AM
> To: Paul Menzel
> Cc: Limonciello, Mario; Andreas Noever; Michael Jamet; Yehezkel Bernat; Christian
> Kellner; linux-kernel@vger.kernel.org; Anthony Wong
> Subject: Re: USB devices on Dell TB16 dock stop working after resuming
>
>
> [EXTERNAL EMAIL]
>
> On Tue, Nov 19, 2019 at 05:55:43PM +0100, Paul Menzel wrote:
> > Dear Mika,
> >
> >
> > On 2019-11-04 17:21, Mika Westerberg wrote:
> > > On Mon, Nov 04, 2019 at 05:11:10PM +0100, Paul Menzel wrote:
> >
> > >> 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 have buildroot based "distro" so there is no UI running.
> >
> > Hmm, this is quite different from the “normal” use-case of the these devices.
> > That way you won’t hit the bugs of the normal users. ;-)
>
> Well, I can install some distro to that thing also :) I suppose Debian
> 10.2 does have this issue, no?
>
> > >>>>> 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.
> > >
> > > I also tried v40 (that was originally on that system) but I was not able
> > > to reproduce it.
> > >
> > > Do you know if the user changed any BIOS settings?
> >
> > We had to disable the Thunderbolt security settings as otherwise the USB
> > devices wouldn’t work at cold boot either.
>
> That does not sound right at all. There is the preboot ACL that allows
> you to use TBT dock aready on boot. Bolt takes care of this.

Yeah it might be useful to enumerate all the BIOS settings that are selected
related to Thunderbolt. Some of them are a bit confusing.

>
> Are you talking about USB devices connected to the TB16 dock?
>
> Also are you connecting the TB16 dock to the Thunderbolt ports (left
> side of the system marked with small lightning logo) or to the normal
> Type-C ports (right side)?

It definitely wouldn't function at all on the right side. The TB16 dock and
cable each contains Alpine Ridge, so it will only work with a TBT controller
on the other end.

>
> > So, I built Linux 5.4-rc8 (`make bindeb-pkg -j8`), but unfortunately the
> > error is still there. Sometimes, re-plugging the dock helped, and sometimes
> > it did not.
> >
> > Please find the logs attached. The strange thing is, the Linux kernel detects
> > the devices and I do not see any disconnect events. But, `lsusb` does not list
> > the keyboard and the mouse. Is that expected.
>
> I'm bit confused. Can you describe the exact steps what you do (so I can
> replicate them).
>
> > Additionally, despite `CONFIG_PCI_DEBUG` I do not see more elaborate
> messages.
>
> I see one strange thing in that log. The Thunderbolt driver does not
> show the device at boot. You should see something like this when you
> boot with the dock connected:
>
> thunderbolt 0-3: new device found, vendor=0xd4 device=0xb051
> thunderbolt 0-3: Dell Dell Thunderbolt Cable
> thunderbolt 0-303: new device found, vendor=0xd4 device=0xb054
> thunderbolt 0-303: Dell Dell Thunderbolt Dock
>
> I only see those after you did suspend/resume cycle.
>
> > Lastly, could the daemon boltd have anything to do with this?
>
> It is the one that authorizes the PCIe tunneling so definitely has
> something to do but below:
>
> >
> > ```
> > $ boltctl --version
> > bolt 0.8
> > $ boltctl list
> > ● Dell Thunderbolt Cable
> > ├─ type: peripheral
> > ├─ name: Dell Thunderbolt Cable
> > ├─ vendor: Dell
> > ├─ uuid: 0082b09d-2f5f-d400-ffff-ffffffffffff
> > ├─ status: authorized
>
> looks what is expected.
\
 
 \ /
  Last update: 2019-11-20 15:16    [W:0.146 / U:0.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site