[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191104162103.GI2552@lahna.fi.intel.com>
Date: Mon, 4 Nov 2019 18:21:03 +0200
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Paul Menzel <pmenzel@...gen.mpg.de>
Cc: Mario Limonciello <mario.limonciello@...l.com>,
Andreas Noever <andreas.noever@...il.com>,
Michael Jamet <michael.jamet@...el.com>,
Yehezkel Bernat <YehezkelShB@...il.com>,
Christian Kellner <ck@...om.net>, linux-kernel@...r.kernel.org,
Anthony Wong <anthony.wong@...onical.com>
Subject: Re: USB devices on Dell TB16 dock stop working after resuming
On Mon, Nov 04, 2019 at 05:11:10PM +0100, Paul Menzel wrote:
> Dear Mika, dear Mario,
>
>
> On 2019-11-04 16:49, Mario.Limonciello@...l.com wrote:
>
> >> From: Mika Westerberg <mika.westerberg@...ux.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.
> >>> 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?
Powered by blists - more mailing lists