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

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: <20191104154446.GH2552@lahna.fi.intel.com>
Date:   Mon, 4 Nov 2019 17:44:46 +0200
From:   Mika Westerberg <mika.westerberg@...ux.intel.com>
To:     Paul Menzel <pmenzel@...gen.mpg.de>
Cc:     Andreas Noever <andreas.noever@...il.com>,
        Michael Jamet <michael.jamet@...el.com>,
        Yehezkel Bernat <YehezkelShB@...il.com>,
        Christian Kellner <ck@...om.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Mario Limonciello <mario.limonciello@...l.com>
Subject: Re: USB devices on Dell TB16 dock stop working after resuming

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:
> > Hi,
> > 
> > On Mon, Nov 04, 2019 at 02:13:13PM +0100, Paul Menzel wrote:
> > > Dear Linux folks,
> > > 
> > > 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?
> 
> 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 :/