Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp4067783yba; Mon, 29 Apr 2019 13:11:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqzRvkFD55NCsSxKxyAuUQOxQkxDk8JX0gWqpA8l+8RmFwiUs4elrlz9JXuSsFN6mpefUwtw X-Received: by 2002:a17:902:86:: with SMTP id a6mr63629864pla.277.1556568668540; Mon, 29 Apr 2019 13:11:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556568668; cv=none; d=google.com; s=arc-20160816; b=UhAwk7L4WzLKeXAEDolGI4GTclWlKxQXMyrG9AY98ckoxm/6aJhJ3Tf+PEBIfzZM6v LtokWps0SlxUMEDQxOJ1XXjwsCevAEZHsQnFtSuiLBaE6GlRy06aygit6ArCgVpMpjOW c2fuwHOHSmDr+D8z3WDgaufYeWvd9po0/T2/3BflCCiT6engz9Zs9jfmo9bYTrIMtsLt 8r/xBjAVo8WsHmyoDBNQwN28573JicAar39wntbAEIN9Y4CICRWfsIPukcVpXISUQiwk w1hQEdYyWsZM5JJFvU4SFXKamDh+4MQkQhBHNNKnRkNHFNBCpdf6dXxnjV2ZUhWnAma4 dvpQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=MvdFa5U3+5xI+n7BnR9vncycYNJ5YsEVOp/2MMs/RVM=; b=J42oruVVlmly7AtEObBIyQ7cFD1SZKypuuVpx0h4n7vdCru5r7AqzIZrDiY4+YEqEP ON3zHl2fm0yQ9eiaJi5dr1kY4Ek4PGlFcgzqhX+vpglJ/9akJpEFcPEok08dEZRM76wM akZx5wV++Il4GXPXIHQaoiXD2suf8n9BtGe6WEtNzJ55Qwvhfg9lRtSASaQCEv29B8oo tdWrGnpTTG919A85tYMpTHifkmiC0/AheIpLMZ1AleiXVtme6sEkbR1CfnlTmsuKeEJw hpQWyIRmQCYaWdyRrjVwyWQY9OPTBhwdfXEmbo43IvSay4/yRB2qQ7ZC9hg3sxjpHUZe chuw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b="BuTnIbE/"; 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=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id bb8si18226642plb.388.2019.04.29.13.10.52; Mon, 29 Apr 2019 13:11:08 -0700 (PDT) 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; dkim=pass header.i=@google.com header.s=20161025 header.b="BuTnIbE/"; 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=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729252AbfD2UJ5 (ORCPT + 99 others); Mon, 29 Apr 2019 16:09:57 -0400 Received: from mail-wm1-f68.google.com ([209.85.128.68]:34244 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728928AbfD2UJ5 (ORCPT ); Mon, 29 Apr 2019 16:09:57 -0400 Received: by mail-wm1-f68.google.com with SMTP id b67so707969wmg.1 for ; Mon, 29 Apr 2019 13:09:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MvdFa5U3+5xI+n7BnR9vncycYNJ5YsEVOp/2MMs/RVM=; b=BuTnIbE/5X9q4mxEOiBag5fyPi2rnHanlZN0p7kPbZG9UotvYf93pZvWrfRxStaYVJ /GdMDmTZmyhQG4Hy8S73PFiykd/3xLz5uxkOlR1T2d+ZYUv3bH1nIvRqSj9TghaMH8e9 h3E7U3EsYofgiT5ZkKI+1mBkQdhp4qVEItwbaVaZiJIbK8xau1AjSVBRICUOm6h7Aakn Lw2n4C1QWRRUPfTk3aM/E0ArH7yQj5h/EqjaiZq3PblxIFSFj0c2riOZT4XPLwvzKElR QNh/o96SuIgP8b1IUBnMZVOJ/BcIXhX8iULCLXLMOueeICaz+P66G7gaXAr4/wbq9wUL XJEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MvdFa5U3+5xI+n7BnR9vncycYNJ5YsEVOp/2MMs/RVM=; b=J34IBx2eU1QirYtrNAf6L3jMa8xmVkcl+qXmNrpelpzuCpevJ88S9spQj8HxtyFok8 dvBZw+mlbK2UGhBYrMD2IEqfygu57nvzVibSbfFcyYA7ocC3cOnDtqLcis0Qe8psmnfu Ba0CETfxEeqxxnlWTsO4yGcq+52s+ih3fHpp39IIxLkVBJ7Uey8uie9IRb6exX3ylvan HHzbuJZbpTJ6mhe/MnFyLerC40F4Vvj6+WZYlzUGqtmucZi3OoTX2/zPFyVNO6KlcMNf e49nhOCecAfD9S3W1y/2DhamDO01rY2bHKBXW91pnsejsUVGndb9BFzkO5lYiKDvE8U9 xmcw== X-Gm-Message-State: APjAAAX3dmJv1HPwlPZGQLgWIw5XGIpIO315nkg7orxBDbrHS5j6MiE1 3XSWewFZ018QQdrkE0aWoWQVeBMqCup9D9YoxecH X-Received: by 2002:a7b:c25a:: with SMTP id b26mr496762wmj.123.1556568595400; Mon, 29 Apr 2019 13:09:55 -0700 (PDT) MIME-Version: 1.0 References: <20190429195459.GU2583@lahna.fi.intel.com> In-Reply-To: <20190429195459.GU2583@lahna.fi.intel.com> From: Bjorn Helgaas Date: Mon, 29 Apr 2019 15:09:43 -0500 Message-ID: Subject: Re: [REGRESSION 5.0.8] Dell thunderbolt dock broken (xhci_hcd and thunderbolt) To: Mika Westerberg Cc: Takashi Iwai , Greg Kroah-Hartman , Lukas Wunner , Jiri Slaby , Michael Hirmke , Linux Kernel Mailing List , Linux PCI Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [+cc linux-pci] On Mon, Apr 29, 2019 at 2:55 PM Mika Westerberg wrote: > > On Mon, Apr 29, 2019 at 09:47:15PM +0200, Takashi Iwai wrote: > > Hi, > > Hi, > > > we've got a regression report wrt xhci_hcd and thunderbolt on a Dell > > machine. 5.0.7 is confirmed to work, so it must be a regression > > introduced by 5.0.8. > > > > The details are found in openSUSE Bugzilla entry: > > https://bugzilla.opensuse.org/show_bug.cgi?id=1132943 > > > > The probe of xhci_hcd on the dock fails like: > > [ 6.269062] pcieport 0000:3a:00.0: enabling device (0006 -> 0007) > > [ 6.270027] pcieport 0000:3b:03.0: enabling device (0006 -> 0007) > > [ 6.270758] xhci_hcd 0000:3c:00.0: init 0000:3c:00.0 fail, -16 > > [ 6.270764] xhci_hcd: probe of 0000:3c:00.0 failed with error -16 > > [ 6.271002] xhci_hcd 0000:3d:00.0: init 0000:3d:00.0 fail, -16 > > > > and later on, thunderbolt gives warnings: > > [ 30.232676] thunderbolt 0000:05:00.0: unexpected hop count: 1023 > > [ 30.232957] ------------[ cut here ]------------ > > [ 30.232958] thunderbolt 0000:05:00.0: interrupt for TX ring 0 is already enabled > > [ 30.232974] WARNING: CPU: 3 PID: 1009 at drivers/thunderbolt/nhi.c:107 ring_interrupt_active+0x1ea/0x230 [thunderbolt] > > > > > > I blindly suspected the commit 3943af9d01e9 and asked for a reverted > > kernel, but in vain. And now it was confirmed that the problem is > > present with the latest 5.1-rc, too. > > > > I put some people who might have interest and the reporter (Michael) > > to Cc. If anyone has an idea, feel free to join to the Bugzilla, or > > let me know if any help needed from the distro side. > > Since it exists in 5.1-rcX also it would be good if someone > who see the problem (Michael?) could bisect it.