From: Simon Richter <Simon.Richter@hogyros.de>
To: linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org
Subject: BAR resizing broken in 6.18 (PPC only?)
Date: Thu, 16 Oct 2025 12:08:46 +0900 [thread overview]
Message-ID: <f9a8c975-f5d3-4dd2-988e-4371a1433a60@hogyros.de> (raw)
Hi,
since switching to 6.18rc1, I get
xe 0030:03:00.0: enabling device (0140 -> 0142)
xe 0030:03:00.0: [drm] unbounded parent pci bridge, device won't support
any PM support.
xe 0030:03:00.0: [drm] Attempting to resize bar from 256MiB -> 16384MiB
xe 0030:03:00.0: BAR 0 [mem 0x620c000000000-0x620c000ffffff 64bit]:
releasing
xe 0030:03:00.0: BAR 2 [mem 0x6200000000000-0x620000fffffff 64bit pref]:
releasing
pci 0030:02:01.0: bridge window [mem 0x6200000000000-0x620001fffffff
64bit pref]: releasing
pci 0030:01:00.0: bridge window [mem 0x6200000000000-0x6203fbff0ffff
64bit pref]: releasing
pci 0030:00:00.0: bridge window [mem 0x6200000000000-0x6203fbff0ffff
64bit pref]: was not released (still contains assigned resources)
pci 0030:02:01.0: disabling bridge window [io 0x0000-0xffffffffffffffff
disabled] to [bus 03] (unused)
pci 0030:02:02.0: disabling bridge window [io 0x0000-0xffffffffffffffff
disabled] to [bus 04] (unused)
pci 0030:02:02.0: disabling bridge window [mem
0x00000000-0xffffffffffffffff 64bit pref disabled] to [bus 04] (unused)
pci 0030:01:00.0: disabling bridge window [io 0x0000-0xffffffffffffffff
disabled] to [bus 02-04] (unused)
pci 0030:00:00.0: Assigned bridge window [mem
0x6200000000000-0x6203fbff0ffff 64bit pref] to [bus 01-04] cannot fit
0x4000000000 required for 0030:01:00.0 bridging to [bus 02-04]
pci 0030:01:00.0: bridge window [mem size 0x3fc0000000 64bit pref] to
[bus 02-04] requires relaxed alignment rules
pci 0030:00:00.0: disabling bridge window [io 0x0000-0xffffffffffffffff
disabled] to [bus 01-04] (unused)
pci 0030:01:00.0: bridge window [mem size 0x3fc0000000 64bit pref]:
can't assign; no space
pci 0030:01:00.0: bridge window [mem size 0x3fc0000000 64bit pref]:
failed to assign
pci 0030:01:00.0: bridge window [mem size 0x3fc0000000 64bit pref]:
can't assign; no space
pci 0030:01:00.0: bridge window [mem size 0x3fc0000000 64bit pref]:
failed to assign
pci 0030:02:01.0: bridge window [mem size 0x400000000 64bit pref]: can't
assign; no space
pci 0030:02:01.0: bridge window [mem size 0x400000000 64bit pref]:
failed to assign
pci 0030:02:01.0: bridge window [mem size 0x400000000 64bit pref]: can't
assign; no space
pci 0030:02:01.0: bridge window [mem size 0x400000000 64bit pref]:
failed to assign
xe 0030:03:00.0: BAR 2 [mem size 0x400000000 64bit pref]: can't assign;
no space
xe 0030:03:00.0: BAR 2 [mem size 0x400000000 64bit pref]: failed to assign
xe 0030:03:00.0: BAR 0 [mem 0x620c000000000-0x620c000ffffff 64bit]: assigned
xe 0030:03:00.0: BAR 0 [mem 0x620c000000000-0x620c000ffffff 64bit]:
releasing
xe 0030:03:00.0: BAR 2 [mem size 0x400000000 64bit pref]: can't assign;
no space
xe 0030:03:00.0: BAR 2 [mem size 0x400000000 64bit pref]: failed to assign
xe 0030:03:00.0: BAR 0 [mem 0x620c000000000-0x620c000ffffff 64bit]: assigned
pci 0030:00:00.0: PCI bridge to [bus 01-04]
pci 0030:00:00.0: bridge window [mem 0x620c000000000-0x620c07fefffff]
pci 0030:00:00.0: bridge window [mem 0x6200000000000-0x6203fbff0ffff
64bit pref]
pci 0030:01:00.0: bridge window [mem 0x6200000000000-0x6203fbff0ffff
64bit pref]: can't claim; address conflict with 0030:01:00.0 [mem
0x6200020000000-0x62000207fffff 64bit pref]
pci 0030:01:00.0: PCI bridge to [bus 02-04]
pci 0030:01:00.0: bridge window [mem 0x620c000000000-0x620c07fefffff]
pci 0030:02:01.0: bridge window [mem 0x6200000000000-0x620001fffffff
64bit pref]: can't claim; no compatible bridge window
pci 0030:02:01.0: PCI bridge to [bus 03]
pci 0030:02:01.0: bridge window [mem 0x620c000000000-0x620c0013fffff]
xe 0030:03:00.0: [drm] Failed to resize BAR2 to 16384M (-ENOSPC).
Consider enabling 'Resizable BAR' support in your BIOS
xe 0030:03:00.0: BAR 2 [mem size 0x10000000 64bit pref]: can't assign;
no space
xe 0030:03:00.0: BAR 2 [mem size 0x10000000 64bit pref]: failed to assign
xe 0030:03:00.0: BAR 2 [mem size 0x10000000 64bit pref]: can't assign;
no space
xe 0030:03:00.0: BAR 2 [mem size 0x10000000 64bit pref]: failed to assign
xe 0030:03:00.0: [drm] Found battlemage (device ID e20b) discrete
display version 14.01 stepping B0
xe 0030:03:00.0: [drm] *ERROR* pci resource is not valid
There's also a bug report[1] on the freedesktop GitLab, but this may be
a more generic problem.
I'm unsure what other "assigned resources" would be below the root that
are not covered by the bridge window of equal size on the upstream port
of the GPU -- also it would be really cool if it reverted to the old
state on failure instead of creating an invalid configuration.
Also, why do we change the BAR assignment while mem decoding is active?
Simon
[1] https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/6356
next reply other threads:[~2025-10-16 3:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 3:08 Simon Richter [this message]
2025-10-16 6:47 ` BAR resizing broken in 6.18 (PPC only?) Manivannan Sadhasivam
2025-10-16 7:26 ` Simon Richter
2025-10-16 15:45 ` Ilpo Järvinen
2025-10-18 18:09 ` Simon Richter
2025-10-21 16:20 ` Ilpo Järvinen
2025-10-22 14:09 ` Simon Richter
2025-10-23 17:42 ` 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=f9a8c975-f5d3-4dd2-988e-4371a1433a60@hogyros.de \
--to=simon.richter@hogyros.de \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 read-only IMAP folder(s) and NNTP newsgroup(s).