From: Oliver Neukum <oneukum@suse.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Kent Lin <kent.lin@canonical.com>,
Linux PCI <linux-pci@vger.kernel.org>,
Linux USB List <linux-usb@vger.kernel.org>
Subject: Re: Titan Ridge xHCI may stop to working after re-plugging the dock
Date: Wed, 10 Jul 2019 13:49:59 +0200 [thread overview]
Message-ID: <1562759399.5312.6.camel@suse.com> (raw)
In-Reply-To: <993E78A1-2A60-46D8-AA51-F4CB077E48D1@canonical.com>
Am Dienstag, den 09.07.2019, 21:10 +0800 schrieb Kai-Heng Feng:
> Hi Mika and Mathias,
>
> I’ve filed a bug [1] which renders docking station unusable.
>
> I am not sure it's a bug in PCI, Thunderbolt or xHCI so raise the issue to
> you both.
>
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=203885
>
> Kai-Heng
>
The issue starts before you unplug. In fact it starts before
the dock is even detected the first time:
[ 13.171167] rfkill: input handler disabled
[ 19.781905] pcieport 0000:00:1c.0: PME: Spurious native interrupt!
[ 19.781909] pcieport 0000:00:1c.0: PME: Spurious native interrupt!
[ 20.109251] usb 4-1: new SuperSpeedPlus Gen 2 USB device number 2 using xhci_hcd
[ 20.136000] usb 4-1: New USB device found, idVendor=0bda, idProduct=0487, bcdDevice= 1.47
[ 20.136004] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 20.136007] usb 4-1: Product: Dell dock
[ 20.136009] usb 4-1: Manufacturer: Dell Inc.
[ 20.140607] hub 4-1:1.0: USB hub found
[ 20.141004] hub 4-1:1.0: 4 ports detected
[ 20.253025] usb 1-4: new high-speed USB device number 5 using xhci_hcd
[ 20.403520] usb 1-4: New USB device found, idVendor=0bda, idProduct=5487, bcdDevice= 1.47
[ 20.403521] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 20.403522] usb 1-4: Product: Dell dock
[ 20.403522] usb 1-4: Manufacturer: Dell Inc.
[ 20.404348] hub 1-4:1.0: USB hub found
This looks like a PCI issue.
In general, this kind of reporting sucks. We have to guess what you did at 19.781905
Regards
Oliver
next prev parent reply other threads:[~2019-07-10 11:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 13:10 Titan Ridge xHCI may stop to working after re-plugging the dock Kai-Heng Feng
2019-07-10 11:49 ` Oliver Neukum [this message]
2019-07-19 7:23 ` Felipe Balbi
2019-07-19 10:29 ` Kai Heng Feng
2019-07-19 10:51 ` Felipe Balbi
2019-07-22 9:44 ` Kai-Heng Feng
2019-07-24 14:45 ` Mathias Nyman
2019-07-25 13:24 ` Kai-Heng Feng
2019-08-13 6:50 ` Kai-Heng Feng
2019-08-14 13:34 ` Mathias Nyman
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=1562759399.5312.6.camel@suse.com \
--to=oneukum@suse.com \
--cc=kai.heng.feng@canonical.com \
--cc=kent.lin@canonical.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.