From: Bjorn Helgaas <helgaas@kernel.org>
To: "Michał Pecio" <michal.pecio@gmail.com>
Cc: linux-pci@vger.kernel.org, "Bjorn Helgaas" <bhelgaas@google.com>,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [REGRESSION 6.14] Some PCI device BARs inacessible
Date: Mon, 16 Mar 2026 15:16:51 -0500 [thread overview]
Message-ID: <20260316201651.GA23314@bhelgaas> (raw)
In-Reply-To: <20250418102926.690ac42c@foxbook>
[+cc Ilpo, +bcc bugzilla reporters and commenters]
On Fri, Apr 18, 2025 at 10:29:26AM +0200, Michał Pecio wrote:
> Hi,
>
> This is a heads up that an apparent PCI regression has been reported
> and mistakenly assigned to USB in the kernel bugzilla:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=220016
>
> Visible symptom is missing USB devices, but the whole controller fails
> to probe, apparently due to devm_request_mem_region() returning NULL,
> see drivers/usb/core/hcd-pci.c and usb_hcd_pci_probe().
>
> Same systems also show a similar failure with some AHCI controller.
> It seems specific to particular ASUS AMD motherboards.
>
> Somebody found that disabling CONFIG_PCI_REALLOC_ENABLE_AUTO helps.
>
> That's all I know, reporters can be reached via bugzilla.
I see some activity in the bugzilla but no resolution. Ilpo has done
a lot of work in this area since v6.14, though, so I wouldn't be
surprised at all if this has been fixed.
Would anybody be interested in testing v6.19 or v7.0-rc to see if this
problem still exists?
Bjorn
next prev parent reply other threads:[~2026-03-16 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 8:29 [REGRESSION 6.14] Some PCI device BARs inacessible Michał Pecio
2025-04-18 16:46 ` Bjorn Helgaas
2026-03-16 20:16 ` Bjorn Helgaas [this message]
2026-03-17 11:47 ` 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=20260316201651.GA23314@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michal.pecio@gmail.com \
--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