linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
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 Mailing List <linux-kernel@vger.kernel.org>,
	Mario Limonciello <mario.limonciello@dell.com>
Subject: Re: USB devices on Dell TB16 dock stop working after resuming
Date: Mon, 4 Nov 2019 17:44:46 +0200	[thread overview]
Message-ID: <20191104154446.GH2552@lahna.fi.intel.com> (raw)
In-Reply-To: <20191104144436.GD2552@lahna.fi.intel.com>

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 :/

  reply	other threads:[~2019-11-04 15:44 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 13:13 USB devices on Dell TB16 dock stop working after resuming Paul Menzel
2019-11-04 14:24 ` Mika Westerberg
2019-11-04 14:44   ` Mika Westerberg
2019-11-04 15:44     ` Mika Westerberg [this message]
2019-11-04 15:49       ` Mario.Limonciello
2019-11-04 16:11         ` Paul Menzel
2019-11-04 16:17           ` Mario.Limonciello
2019-11-04 16:22             ` Paul Menzel
2019-11-04 16:21           ` Mika Westerberg
2019-11-19 16:55             ` Paul Menzel
2019-11-19 17:20               ` Paul Menzel
2019-11-20 10:50               ` Mika Westerberg
2019-11-20 14:15                 ` Mario.Limonciello
2019-11-20 15:23                   ` Mika Westerberg
2019-11-20 17:06                     ` Mario.Limonciello
2019-11-20 17:16                       ` Yehezkel Bernat
2019-11-20 17:41                         ` Mario.Limonciello
2019-11-20 17:43                         ` Mika Westerberg
2019-11-20 17:39                       ` Mika Westerberg
2019-11-22 10:50                 ` Mika Westerberg
2019-11-22 11:05                   ` Paul Menzel
2019-11-22 11:29                     ` Mika Westerberg
2019-11-22 11:33                       ` Paul Menzel
2019-11-22 11:41                         ` Mika Westerberg
2019-11-25  9:20                           ` Mathias Nyman
2019-11-26 11:33                             ` Paul Menzel
2019-11-26 12:44                               ` Mathias Nyman
2019-12-20 14:25                                 ` Paul Menzel
2019-12-23  9:39                                   ` Mathias Nyman
2020-01-17  9:56                                     ` Paul Menzel
2020-01-17 18:33                                       ` Mario.Limonciello
2020-01-18  9:15                                         ` Paul Menzel
2020-01-27 22:16                                           ` Paul Menzel
2020-02-05 13:10                                             ` Paul Menzel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191104154446.GH2552@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=ck@xatom.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@dell.com \
    --cc=michael.jamet@intel.com \
    --cc=pmenzel@molgen.mpg.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).