Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: bjorn@helgaas.com
Cc: "Linux PCI" <linux-pci@vger.kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: Fwd: [Bug 221457] New: PCI core drops Resizable BAR sizing after ASPM common-clock reconfiguration on Thunderbolt/USB4 hot-plug link
Date: Mon, 4 May 2026 13:43:25 -0500	[thread overview]
Message-ID: <20260504184325.GA656008@bhelgaas> (raw)
In-Reply-To: <CABhMZUVSiQM+KAXeEFCPJSnQFq1Bc7F6GZys1ucfpE0Gs+3V6A@mail.gmail.com>

[+bcc reporter]

On Mon, May 04, 2026 at 01:29:28PM -0500, Bjorn Helgaas wrote:
> ---------- Forwarded message ---------
> https://bugzilla.kernel.org/show_bug.cgi?id=221457
> ...
> SUMMARY
> 
> Initial PCI enumeration assigns BAR 1 = 16 GB on an RTX 5060 Ti behind a
> Thunderbolt 4 link. Shortly after, the pcieport ASPM service runs a
> common-clock reconfigure on the host root port, the downstream bridges go
> through [bus 00-00] reset and re-enumeration, and BAR 1 is reassigned at 256
> MB.

stuck-tamer-growl: Thanks for the report.  Would you mind collect the
complete dmesg log and the output of "sudo lspci -vv" and posting them
here (or in the bugzilla if you prefer)?

  reply	other threads:[~2026-05-04 18:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-221457-41252@https.bugzilla.kernel.org/>
2026-05-04 18:29 ` Fwd: [Bug 221457] New: PCI core drops Resizable BAR sizing after ASPM common-clock reconfiguration on Thunderbolt/USB4 hot-plug link Bjorn Helgaas
2026-05-04 18:43   ` Bjorn Helgaas [this message]
     [not found]     ` <AB2EBCFC-663F-48A1-9C11-2DFB7C844B19.1@smtp-inbound1.duck.com>
2026-05-06  5:09       ` stuck-tamer-growl
2026-05-06 12:26         ` Ilpo Järvinen
2026-05-06 12:38           ` Mika Westerberg
2026-05-06 13:07             ` Mario Limonciello
2026-05-06 14:44               ` Mika Westerberg

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=20260504184325.GA656008@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bjorn@helgaas.com \
    --cc=ilpo.jarvinen@linux.intel.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