linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 14 Aug 2020 21:36:33 +0000	[thread overview]
Message-ID: <bug-208891-208809-ovGRCfD7jA@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 #22 from Matt Turner (mattst88@gmail.com) ---
(In reply to Mika Westerberg from comment #21)
> Thanks for the logs. For some reason the two downstream PCIe ports (2d:00.0
> and 2d:01.0) that lead to the xHCI and the NIC get their bridge windows
> reset to 0 and this prevents drivers from accessing their MMIO registers. I
> also see that you are not running the mainline kernel so can you take v5.8
> vanilla kernel and try that and add "pcie_port_pm=off" to the kernel command
> line to disable runtime PM of those ports.

Tried with v5.8.1. Was previously using 5.8.0-rc7-next-20200729 because I
expected to be asked to test linux-next.

Anyway, pcie_port_pm=off didn't help. Neither did pcie_ports=native.

I also tried adding

+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL,  0x1578, quirk_no_bus_reset);

to drivers/pci/quirks.c on a whim because of something I saw in a google
search, but of course that didn't help either.

Is the fact that it works if I attach the dock and then boot the system not
indicative of something? Is the BIOS/EFI setup tasked with programming some
stuff that the thunderbolt driver might be failing to do so?

I just noticed something odd. Coldplugged with the dock working, I can suspend
and resume and it will continue working. But if I unplug and replug the dock
while the system is suspended, it fails to work after resume.

Doesn't that indicate that the thunderbolt firmware is doing something wrong?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-08-14 21:36 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 [this message]
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-ovGRCfD7jA@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).