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 13:24:26 +0000 [thread overview]
Message-ID: <bug-208891-208809-yD96IYJwa7@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 #32 from Mika Westerberg (mika.westerberg@linux.intel.com) ---
Thanks for the logs. I think I know what is going on. From the failure log:
Registers get saved:
[ 80.292442] pci 0000:2d:00.0: saving config space at offset 0x1c (reading
0x101)
[ 80.292446] pci 0000:2d:00.0: saving config space at offset 0x20 (reading
0x0)
[ 80.292450] pci 0000:2d:00.0: saving config space at offset 0x24 (reading
0x10001)
[ 80.292454] pci 0000:2d:00.0: saving config space at offset 0x28 (reading
0x0)
[ 80.292458] pci 0000:2d:00.0: saving config space at offset 0x2c (reading
0x0)
Resources are assigned:
[ 80.293725] pci 0000:2d:00.0: BAR 8: assigned [mem 0x68000000-0x680fffff]
[ 80.293727] pci 0000:2d:00.0: BAR 9: assigned [mem 0x6000000000-0x60000fffff
64bit pref]
[ 80.293752] pci 0000:2d:00.0: BAR 7: assigned [io 0x5000-0x5fff]
...
[ 80.293803] pci 0000:2d:00.0: PCI bridge to [bus 2e]
[ 80.293807] pci 0000:2d:00.0: bridge window [io 0x5000-0x5fff]
[ 80.293816] pci 0000:2d:00.0: bridge window [mem 0x68000000-0x680fffff]
[ 80.293823] pci 0000:2d:00.0: bridge window [mem 0x6000000000-0x60000fffff
64bit pref]
Note that there is no save happening here. Then shortly after there is register
restore:
[ 80.294748] pcieport 0000:2d:00.0: runtime IRQ mapping not provided by arch
[ 80.294830] pcieport 0000:2d:00.0: restoring config space at offset 0x2c
(was 0x60, writing 0x0)
[ 80.294835] pcieport 0000:2d:00.0: restoring config space at offset 0x28
(was 0x60, writing 0x0)
[ 80.294839] pcieport 0000:2d:00.0: restoring config space at offset 0x24
(was 0x10001, writing 0x10001)
[ 80.294844] pcieport 0000:2d:00.0: restoring config space at offset 0x20
(was 0x68006800, writing 0x0)
^^^^^^^^^^ ^^^
[ 80.294848] pcieport 0000:2d:00.0: restoring config space at offset 0x1c
(was 0x5151, writing 0x101)
This ends up clearing the bridge window registers of 2d:00.0 downstream port. I
guess this does not happen always because it is dependent on timing.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-08-31 13:24 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 [this message]
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-yD96IYJwa7@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).