From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Jonas Höglund" <firefly@firefly.nu>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [REGRESSION] amdgpu with Thunderbolt eGPU bracket fails since new bridge window alignment calculation code
Date: Tue, 7 Apr 2026 10:37:43 +0300 (EEST) [thread overview]
Message-ID: <db715a3b-80c7-31ed-bf31-fb55ad7c538c@linux.intel.com> (raw)
In-Reply-To: <d50a8eb1-3a16-47c7-bfea-0a3def606c6f@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
On Thu, 2 Apr 2026, Jonas Höglund wrote:
> On Thu, 2 Apr 2026, at 16:51, Jonas Höglund wrote:
> > Here are dmesg logs (with the appropriate dyndbg cmdline flag) for both
> > cases, in case it's useful:
> >
> > https://up.firefly.nu/pub/amdgpu-egpu-crash-7.0.0-rc6.dmesg.txt
> > https://up.firefly.nu/pub/amdgpu-egpu-good-pci-resource.dmesg.txt
>
> Actually, now that I look closer at the good-case dmesg (just after
> sending the email, typical), I guess I'm not sure how happy the driver
> and dock really are. Well, I'll let you weigh in since you're more
> intimately familiar with the subsystem and expected debug messages.
Hi,
Even the "good" case does fail to enlarge the eGPU resource because some
of the upstream bridge window are pinned by other resources.
It is a problem that has come up multiple times over the past few years
but it's also a problem that is not very easy to solve (but I'm working on
it). The sizing needs to be corrected earlier than that point (before the
other resources pin those bridge windows), at the time we discover that
BAR resize fails, it's already way too late to correct things.
--
i.
next prev parent reply other threads:[~2026-04-07 7:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 23:02 [REGRESSION] amdgpu with Thunderbolt eGPU bracket fails since new bridge window alignment calculation code Jonas Höglund
2026-03-28 8:46 ` Thorsten Leemhuis
2026-03-28 16:09 ` Jonas Höglund
2026-03-30 7:21 ` Thorsten Leemhuis
2026-03-30 14:33 ` Ilpo Järvinen
2026-03-30 15:50 ` Jonas Höglund
2026-03-30 16:32 ` Ilpo Järvinen
2026-04-02 16:51 ` Jonas Höglund
2026-04-02 16:56 ` Jonas Höglund
2026-04-07 7:37 ` Ilpo Järvinen [this message]
2026-04-07 7:26 ` Ilpo Järvinen
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=db715a3b-80c7-31ed-bf31-fb55ad7c538c@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=firefly@firefly.nu \
--cc=linux-pci@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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