From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Michal Babička" <michal.babka@gmail.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [WARNING: UNSCANNABLE EXTRACTION FAILED][BUG] Apple Mac mini 2018 + Thunderbolt 3 eGPU: PCI bridge window / BAR allocation failure prevents NVIDIA and AMD GPUs from initializing
Date: Fri, 27 Mar 2026 19:54:06 +0200 (EET) [thread overview]
Message-ID: <da0ede48-3197-e3df-a83a-4e0028b5f5c5@linux.intel.com> (raw)
In-Reply-To: <CAF4axAei9zwKrWrcoHQE65D2xY=mWS0onRAGxyjX0p2a+jXmUQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2278 bytes --]
On Tue, 24 Mar 2026, Michal Babička wrote:
> Hello,
>
> I am reporting a reproducible PCI resource allocation problem on an
> Apple Mac mini 2018 with a Thunderbolt 3 eGPU enclosure.
>
> Hardware:
>
> Apple Mac mini 2018
> Razer Core X Chroma
> NVIDIA GPU tested
> AMD Radeon Vega 64 tested
> Zorin OS 18 Pro
> kernels tested: 6.12.x and 6.17.x
>
> Problem summary:
> The eGPU enclosure and GPU are detected and enumerated on the PCI bus,
> but GPU initialization fails because PCI bridge windows / BAR
> resources are not assigned correctly.
>
> This reproduces with multiple GPU vendors in the same enclosure on the
> same host, which suggests a PCI / Thunderbolt bridge resource
> allocation problem on this platform rather than a vendor-specific
> driver issue.
>
> Expected behavior:
> The kernel should assign valid PCI bridge windows and BAR resources so
> the GPU can initialize successfully and become usable.
>
> Actual behavior:
> The GPU is visible on the PCI bus, but bridge windows and BAR
> resources are incomplete or invalid, leaving the device unusable.
>
> Observed errors include:
>
> bridge window [mem size ...]: can't assign; no space
> NVRM: BAR1 is 0M @ 0x0
> RmInitAdapter failed
> NVIDIA initialization fails
> AMD shows similar behavior in the same enclosure on the same host
>
> Kernel command line used for the latest debug boot:
> BOOT_IMAGE=/boot/vmlinuz-6.17.0-19-generic
> root=UUID=f0048c61-b4fe-4edb-9af5-bc756f9e2e7d ro quiet splash
> "dyndbg=file drivers/pci/* +p" vt.handoff=7
>
> I also confirmed that dynamic debug for drivers/pci was enabled.
>
> I collected and attached two archives:
>
> egpu-logs.tar.gz
> egpu-logs-dyndbg.tar.gz
>
> These archives contain:
>
> full dmesg
> dmesg extract
> lspci -nnvvv
> lspci tree
> per-device lspci dumps for the relevant bridges and GPU
> /proc/iomem
> journalctl -b
> nvidia-smi output
>
> Please let me know which specific logs or excerpts would be most useful.
Did you have any logs with pci=realloc. There are those claiming conflicts
resulting in clipping bridge windows from their original size so I'm
skeptical this case will work well without kernel rearranging the bridge
windows.
--
i.
prev parent reply other threads:[~2026-03-27 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 7:34 [BUG] Apple Mac mini 2018 + Thunderbolt 3 eGPU: PCI bridge window / BAR allocation failure prevents NVIDIA and AMD GPUs from initializing Michal Babička
2026-03-27 17:54 ` Ilpo Järvinen [this message]
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=da0ede48-3197-e3df-a83a-4e0028b5f5c5@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=michal.babka@gmail.com \
/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