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>,
"Joe Doss" <joe@solidadmin.com>
Subject: Re: [REGRESSION 6.14] Some PCI device BARs inacessible
Date: Fri, 18 Apr 2025 11:46:56 -0500 [thread overview]
Message-ID: <20250418164656.GA160194@bhelgaas> (raw)
In-Reply-To: <20250418102926.690ac42c@foxbook>
[+cc Joe (reporter), Ilpo]
[+bcc Steven (another reporter, bcc since email hasn't been used publicly recently]
On Fri, Apr 18, 2025 at 10:29:26AM +0200, Michał Pecio wrote:
> 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.
#regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=220016
next prev parent reply other threads:[~2025-04-18 16:46 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 [this message]
2026-03-16 20:16 ` Bjorn Helgaas
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=20250418164656.GA160194@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=joe@solidadmin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.