Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Xiaochun Lee <lixc17@lenovo.com>
Subject: Re: [Bug 219547] New: BAR 6 ROM BAR failed to assign even their host bridge has enough space
Date: Tue, 21 Jan 2025 16:19:38 -0600	[thread overview]
Message-ID: <20250121221938.GA990381@bhelgaas> (raw)
In-Reply-To: <bug-219547-41252@https.bugzilla.kernel.org/>

On Mon, Dec 02, 2024 at 08:07:21AM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=219547
> 
>             Bug ID: 219547
>            Summary: BAR 6 ROM BAR failed to assign even their host bridge
>                     has enough space
>           Reporter: lixc17@lenovo.com
>         Regression: No
> 
> Created attachment 307307
>   --> https://bugzilla.kernel.org/attachment.cgi?id=307307&action=edit
> command dmesg output
> 
> kernel message output includes below error messages when assign ROM BAR for
> some device on Intel Birch Stream platform.
> -->>
> [   15.058116] pci 0000:3b:00.0: ROM [mem size 0x00100000 pref]: can't assign;
> no space
> [   15.058121] pci 0000:3b:00.0: ROM [mem size 0x00100000 pref]: failed to
> assign
> <<--

Thanks for the report!

Many more details, dmesg (from v6.8), lspci already attached to
bugzilla.

Would be helpful if you could reproduce this on a current kernel,
e.g., v6.13, and attach that dmesg log, to make sure it's not
something that's already been fixed.

Bjorn

           reply	other threads:[~2025-01-21 22:19 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-219547-41252@https.bugzilla.kernel.org/>]

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=20250121221938.GA990381@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lixc17@lenovo.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