From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 208891] New: Thunderbolt hotplug fails on HP x360 13t-aw000/86FA with HP Thunderbolt 3 Dock
Date: Wed, 12 Aug 2020 22:17:16 +0000 [thread overview]
Message-ID: <bug-208891-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=208891
Bug ID: 208891
Summary: Thunderbolt hotplug fails on HP x360 13t-aw000/86FA
with HP Thunderbolt 3 Dock
Product: Drivers
Version: 2.5
Kernel Version: 5.8.0
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: mattst88@gmail.com
Regression: No
Created attachment 290843
--> https://bugzilla.kernel.org/attachment.cgi?id=290843&action=edit
Kernel .config
My HP Spectre x360 (Icelake) laptop doesn't successfully hotplug with an HP
Thunderbolt 3 dock. I'm using 5.8.0-rc7-next-20200729. The dock's firmwares
have been updated from a system running Windows. The HP laptop is using the
latest BIOS as of last week, and nvm_version is "80.0":
% cat /sys/devices/pci0000:00/0000:00:0d.2/domain0/0-0/nvm_version
80.0
Cold booting the system with the dock attached provides working ethernet, USB
hub, etc. Unplugging and replugging the dock does not work, leaving it only
providing power.
Attached are dmesg, lspci -vvnnt output, and /proc/iomem captured (1) at
coldboot with the dock attached, (2) after unplugging the dock, (3) after
hotplugging the dock, and (4) after hotplugging the dock when it had not been
previously attached; and my kernel .config.
For search engines, the most apparent failure in dmesg is:
xhci_hcd 0000:2e:00.0: enabling device (0000 -> 0002)
xhci_hcd 0000:2e:00.0: xHCI Host Controller
xhci_hcd 0000:2e:00.0: new USB bus registered, assigned bus number 5
xhci_hcd 0000:2e:00.0: Host halt failed, -19
xhci_hcd 0000:2e:00.0: can't setup: -19
xhci_hcd 0000:2e:00.0: USB bus 5 deregistered
xhci_hcd 0000:2e:00.0: init 0000:2e:00.0 fail, -19
tg3 0000:2f:00.0: enabling device (0000 -> 0002)
tg3 0000:2f:00.0: phy probe failed, err -19
tg3 0000:2f:00.0: Problem fetching invariants of chip, aborting
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-08-12 22:17 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 22:17 bugzilla-daemon [this message]
2020-08-12 22:18 ` [Bug 208891] Thunderbolt hotplug fails on HP x360 13t-aw000/86FA with HP Thunderbolt 3 Dock bugzilla-daemon
2020-08-12 22:18 ` bugzilla-daemon
2020-08-12 22:18 ` bugzilla-daemon
2020-08-12 22:19 ` bugzilla-daemon
2020-08-12 22:19 ` bugzilla-daemon
2020-08-12 22:19 ` bugzilla-daemon
2020-08-12 22:20 ` bugzilla-daemon
2020-08-12 22:20 ` bugzilla-daemon
2020-08-12 22:20 ` bugzilla-daemon
2020-08-12 22:34 ` bugzilla-daemon
2020-08-12 22:34 ` bugzilla-daemon
2020-08-12 22:39 ` bugzilla-daemon
2020-08-13 8:18 ` bugzilla-daemon
2020-08-13 17:32 ` bugzilla-daemon
2020-08-14 6:54 ` bugzilla-daemon
2020-08-14 6:56 ` bugzilla-daemon
2020-08-14 7:09 ` bugzilla-daemon
2020-08-14 7:09 ` bugzilla-daemon
2020-08-14 7:15 ` bugzilla-daemon
2020-08-14 7:15 ` bugzilla-daemon
2020-08-14 12:51 ` bugzilla-daemon
2020-08-14 21:36 ` bugzilla-daemon
2020-08-17 10:43 ` bugzilla-daemon
2020-08-19 14:00 ` bugzilla-daemon
2020-08-23 19:02 ` bugzilla-daemon
2020-08-27 19:57 ` bugzilla-daemon
2020-08-27 19:58 ` bugzilla-daemon
2020-08-27 19:59 ` bugzilla-daemon
2020-08-27 20:00 ` bugzilla-daemon
2020-08-27 20:06 ` bugzilla-daemon
2020-08-31 13:24 ` bugzilla-daemon
2020-08-31 19:30 ` bugzilla-daemon
2020-08-31 19:30 ` bugzilla-daemon
2020-08-31 19:37 ` bugzilla-daemon
2020-08-31 19:40 ` bugzilla-daemon
2020-09-04 20:28 ` bugzilla-daemon
2020-09-29 19:32 ` bugzilla-daemon
2020-09-29 19:33 ` bugzilla-daemon
2020-10-12 18:30 ` bugzilla-daemon
2020-10-20 7:33 ` bugzilla-daemon
2020-11-01 16:20 ` bugzilla-daemon
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=bug-208891-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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).