Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp2133225ybc; Wed, 20 Nov 2019 09:22:40 -0800 (PST) X-Google-Smtp-Source: APXvYqxskO605Fy6HPJNptjjbUjt6fKXuhfHCzsOM5C8PiK6p+QP2Tk6EsWpS5eUigykllozWJzN X-Received: by 2002:a17:906:c7d0:: with SMTP id dc16mr6767804ejb.73.1574270560385; Wed, 20 Nov 2019 09:22:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574270560; cv=none; d=google.com; s=arc-20160816; b=zGaXhu1IBynN/Nc8IQSn6miCPR0dCjmDCcQFWGWesSxJTQtbaIAL8l/TGEc//1f/vD 2bo/rxB2VAxMvinm84+L1B/t/+O+E3YjWSYkcAr+frLOJxZLZd5xx9ShxuZ7sax+WYcY gFJbkgw9OzV/NeAWtp19PTX/8KS9M8P6bZMafdzmUpzCa9opTSIahFHT3lLdJ3WOWrfR IVVJOAm91n/iuwc7s8qsAD8yk7TnFtpQeCFgIsZ6MBeDMXavIp83q0Wbnft96hZH1QHG Je76DdZxsIi1+mK8ZB6J0SqpUnWkldZM+yUgtnkq4Ha7l2dVUmI8N1ehBypdSMNGM7IM JYwA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:organization:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=6LTJgCTQhYIumPrtuHIJVrW8ER4uPnFfjxranRyrJGM=; b=CYHpb3EDGMSnTfjjZCXLWlPPq4CGlDYwqJ4zDS8io10oVtT+G8kxxCD+AdizfjZVYy Kk6sajqLSAwJ/tCUe+ItCqryPawLf/l3LNQ1HoGQUPupzbSCkFEV8XiwzX+rNIxo16ga GWD3zjhuMZfaxgfTl1mgX/UVv7lzfWb84Fvi11enpw+p/1SV2Gi7B9ZttHBXuCbOFB46 Y4wWV2HCVCMrK/z/l05ABN2BuunN29WJnuaPLd7xYCM9OXFzBXPGGyYEQLEevxw1IR5h xjWSp6rWNHMXl7O//OwutA5174jlGbSTvrdj5OcWfbnQ3eS9PehAAH01G1iPJt2cJNcC D0jg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g6si7694290ejm.42.2019.11.20.09.22.16; Wed, 20 Nov 2019 09:22:40 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728850AbfKTPYH (ORCPT + 99 others); Wed, 20 Nov 2019 10:24:07 -0500 Received: from mga06.intel.com ([134.134.136.31]:23795 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727659AbfKTPYG (ORCPT ); Wed, 20 Nov 2019 10:24:06 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Nov 2019 07:23:56 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,222,1571727600"; d="scan'208";a="215833737" Received: from lahna.fi.intel.com (HELO lahna) ([10.237.72.163]) by fmsmga001.fm.intel.com with SMTP; 20 Nov 2019 07:23:52 -0800 Received: by lahna (sSMTP sendmail emulation); Wed, 20 Nov 2019 17:23:51 +0200 Date: Wed, 20 Nov 2019 17:23:51 +0200 From: Mika Westerberg To: Mario.Limonciello@dell.com Cc: pmenzel@molgen.mpg.de, andreas.noever@gmail.com, michael.jamet@intel.com, YehezkelShB@gmail.com, ck@xatom.net, linux-kernel@vger.kernel.org, anthony.wong@canonical.com Subject: Re: USB devices on Dell TB16 dock stop working after resuming Message-ID: <20191120152351.GJ11621@lahna.fi.intel.com> References: <5d2b39bc-5952-c2b6-63b3-bce28122ffd5@molgen.mpg.de> <20191104142459.GC2552@lahna.fi.intel.com> <20191104144436.GD2552@lahna.fi.intel.com> <20191104154446.GH2552@lahna.fi.intel.com> <20191104162103.GI2552@lahna.fi.intel.com> <20191120105048.GY11621@lahna.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 20, 2019 at 02:15:17PM +0000, Mario.Limonciello@dell.com wrote: > > -----Original Message----- > > From: Mika Westerberg > > 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 > > > >>>> 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. BTW, I played a bit with 9380 and it looks like there is no option to enable Preboot ACL which means that if you have TBT security enabled (user or secure) the Dock PCIe side is not functional during boot, only once the OS has booted up. That's fine unless you want to enter BIOS menu from the keyboard you have connected to the TB16 dock (probably not too common use case anyway).