From: Bjorn Helgaas <bhelgaas@google.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lukas Wunner <lukas@wunner.de>, Jiri Slaby <jslaby@suse.cz>,
Michael Hirmke <opensuse@mike.franken.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: [REGRESSION 5.0.8] Dell thunderbolt dock broken (xhci_hcd and thunderbolt)
Date: Mon, 29 Apr 2019 15:09:43 -0500 [thread overview]
Message-ID: <CAErSpo4awEXF3evh7=ZGi39y1dpMx9bdhXw8zt7s+1sDaH6nng@mail.gmail.com> (raw)
In-Reply-To: <20190429195459.GU2583@lahna.fi.intel.com>
[+cc linux-pci]
On Mon, Apr 29, 2019 at 2:55 PM Mika Westerberg
<mika.westerberg@linux.intel.com> 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.
prev parent reply other threads:[~2019-04-29 20:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 19:47 [REGRESSION 5.0.8] Dell thunderbolt dock broken (xhci_hcd and thunderbolt) Takashi Iwai
2019-04-29 19:54 ` Mika Westerberg
2019-04-29 20:03 ` Michael Hirmke
2019-04-29 20:13 ` Mika Westerberg
2019-04-29 20:36 ` Mika Westerberg
2019-04-29 22:07 ` Takashi Iwai
2019-04-30 8:39 ` Michael Hirmke
2019-04-30 9:00 ` Mika Westerberg
2019-04-30 9:37 ` Rafael J. Wysocki
2019-05-02 11:48 ` Greg Kroah-Hartman
2019-05-03 23:35 ` Furquan Shaikh
2019-05-06 6:45 ` Mika Westerberg
2019-05-09 11:52 ` Furquan Shaikh
2019-04-29 20:09 ` Bjorn Helgaas [this message]
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='CAErSpo4awEXF3evh7=ZGi39y1dpMx9bdhXw8zt7s+1sDaH6nng@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mika.westerberg@linux.intel.com \
--cc=opensuse@mike.franken.de \
--cc=tiwai@suse.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).