From: Bjorn Helgaas <helgaas@kernel.org>
To: Kenneth Crudup <kenny@panix.com>
Cc: ilpo.jarvinen@linux.intel.com,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: Commit 4292a1e45fd4 ("PCI: Refactor distributing available memory to use loops") gives errors enumerating TBolt devices behind my TB dock
Date: Wed, 8 Oct 2025 15:14:43 -0500 [thread overview]
Message-ID: <20251008201443.GA638724@bhelgaas> (raw)
In-Reply-To: <dd551b81-9e81-480b-aab3-7cf8b8bbc1d0@panix.com>
On Tue, Oct 07, 2025 at 02:39:09PM -0700, Kenneth Crudup wrote:
>
> I'm running Linus' master (as of a8cdf51cda30).
>
> I have a Thunderbolt dock (Amazon Basics generic thing, but it also happens
> on my CalDigit TB4). With the above commit (and aaae2863e731 ("PCI: Refactor
> remove_dev_resources() to use pbus_select_window()), so the Subject: commit
> would come out cleanly) if I plug in a TB device past my TB Dock, they don't
> fully enumerate (i.e., no DP tunneling, no partitions created, etc.)
Can you try this patch, which identified the same 4292a1e45fd4 commit?
https://lore.kernel.org/r/tencent_8C54420E1B0FF8D804C1B4651DF970716309@qq.com
I tentatively put it on pci/for-linus.
next prev parent reply other threads:[~2025-10-08 20:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 21:39 Commit 4292a1e45fd4 ("PCI: Refactor distributing available memory to use loops") gives errors enumerating TBolt devices behind my TB dock Kenneth Crudup
2025-10-07 23:02 ` Kenneth Crudup
2025-10-08 8:10 ` Ilpo Järvinen
2025-10-08 14:27 ` Kenneth Crudup
2025-10-08 14:57 ` Kenneth Crudup
2025-10-08 20:14 ` Bjorn Helgaas [this message]
2025-10-08 20:30 ` Kenneth Crudup
2025-10-08 20:58 ` Bjorn Helgaas
2025-10-08 21:20 ` Kenneth Crudup
2025-10-08 21:51 ` Bjorn Helgaas
2025-10-08 21:14 ` Kenneth Crudup
2025-10-08 21:52 ` Bjorn Helgaas
2025-10-08 21:54 ` Kenneth Crudup
2025-10-08 21:53 ` Kenneth Crudup
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=20251008201443.GA638724@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kenny@panix.com \
--cc=linux-pci@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