From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 208891] Thunderbolt hotplug fails on HP x360 13t-aw000/86FA with HP Thunderbolt 3 Dock
Date: Mon, 31 Aug 2020 19:37:29 +0000 [thread overview]
Message-ID: <bug-208891-208809-bb5XkGr6Rs@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208891-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208891
--- Comment #36 from Matt Turner (mattst88@gmail.com) ---
Dang, doesn't work, but it the lspci output looks like we're getting the right
memory addresses (diffing against the attached lspci -vv success output).
--- lspci 2020-08-31 12:16:11.919502424 -0700
+++ lspci-patched-success 2020-08-27 12:47:04.525430133 -0700
@@ -1025,13 +1025,14 @@
2e:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1042A USB 3.0 Host
Controller [1b21:1142] (prog-if 30 [XHCI])
Subsystem: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
[1b21:1142]
- Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
+ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
+ Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 16
- Region 0: Memory at 68000000 (64-bit, non-prefetchable) [virtual]
[size=32K]
+ Region 0: Memory at 68000000 (64-bit, non-prefetchable) [size=32K]
Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
- Capabilities: [68] MSI-X: Enable- Count=8 Masked-
+ Capabilities: [68] MSI-X: Enable+ Count=8 Masked-
Vector table: BAR=0 offset=00002000
PBA: BAR=0 offset=00002080
Capabilities: [78] Power Management version 3
@@ -1071,14 +1072,16 @@
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
+ Kernel driver in use: xhci_hcd
2f:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme
BCM57762 Gigabit Ethernet PCIe [14e4:1682] (rev 01)
Subsystem: Broadcom Inc. and subsidiaries NetXtreme BCM57762 Gigabit
Ethernet PCIe [14e4:1682]
- Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
+ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
+ Latency: 0
Interrupt: pin A routed to IRQ 17
- Region 0: Memory at 6000100000 (64-bit, prefetchable) [virtual]
[size=64K]
- Region 2: Memory at 6000110000 (64-bit, prefetchable) [virtual]
[size=64K]
+ Region 0: Memory at 6000100000 (64-bit, prefetchable) [size=64K]
+ Region 2: Memory at 6000110000 (64-bit, prefetchable) [size=64K]
Capabilities: [48] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
And the diff against the lspci -vv hotplug failure attachment:
--- lspci 2020-08-31 12:16:11.919502424 -0700
+++ lspci-patched-failure 2020-08-27 12:54:22.300504263 -0700
@@ -654,9 +654,9 @@
Latency: 0
Interrupt: pin A routed to IRQ 167
Bus: primary=2d, secondary=2e, subordinate=2e, sec-latency=0
- I/O behind bridge: 00005000-00005fff [size=4K]
- Memory behind bridge: 68000000-680fffff [size=1M]
- Prefetchable memory behind bridge: 0000006000000000-00000060000fffff
[size=1M]
+ I/O behind bridge: 00000000-00000fff [size=4K]
+ Memory behind bridge: 00000000-000fffff [size=1M]
+ Prefetchable memory behind bridge: 0000000000000000-00000000000fffff
[size=1M]
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
So the memory addresses look right, but we're missing "[virtual]". Hopefully
that indicates only a small remaining problem :)
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-08-31 19:37 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 22:17 [Bug 208891] New: Thunderbolt hotplug fails on HP x360 13t-aw000/86FA with HP Thunderbolt 3 Dock bugzilla-daemon
2020-08-12 22:18 ` [Bug 208891] " 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 [this message]
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-bb5XkGr6Rs@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 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.