From: Bjorn Helgaas <helgaas@kernel.org>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: linux-pci@vger.kernel.org,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: pcie: kernel log - BAR 15: no space for... BAR 15: failed to assign..
Date: Mon, 10 Feb 2020 16:28:34 -0600 [thread overview]
Message-ID: <20200210222834.GA74627@google.com> (raw)
In-Reply-To: <CAHhAz+j9ukzVia8_V3FisLCpT2GsKbmhWtJpQudtWUJcSAki+w@mail.gmail.com>
On Sun, Feb 09, 2020 at 07:59:41AM +0530, Muni Sekhar wrote:
> Hi all,
>
> After rebooting the system following messages are seen in dmesg.
> Not sure if these indicate a problem. Can some one look at these and
> confirm if this is problem or can be ignored ?
>
> Also any suggestions as to what would cause this?
>
> [ 1.084728] pci 0000:00:1c.0: BAR 15: no space for [mem size
> 0x00200000 64bit pref]
> [ 1.084813] pci 0000:00:1c.0: BAR 15: failed to assign [mem size
> 0x00200000 64bit pref]
> [ 1.084890] pci 0000:00:1c.2: BAR 14: no space for [mem size 0x00200000]
> [ 1.084949] pci 0000:00:1c.2: BAR 14: failed to assign [mem size 0x00200000]
> [ 1.085037] pci 0000:00:1c.2: BAR 15: no space for [mem size
> 0x00200000 64bit pref]
> [ 1.085108] pci 0000:00:1c.2: BAR 15: failed to assign [mem size
> 0x00200000 64bit pref]
> [ 1.085199] pci 0000:00:1c.3: BAR 15: no space for [mem size
> 0x00200000 64bit pref]
> [ 1.085270] pci 0000:00:1c.3: BAR 15: failed to assign [mem size
> 0x00200000 64bit pref]
> [ 1.085343] pci 0000:00:1c.0: BAR 13: assigned [io 0x1000-0x1fff]
> [ 1.085403] pci 0000:00:1c.2: BAR 13: assigned [io 0x2000-0x2fff]
> [ 1.085470] pci 0000:00:1c.3: BAR 15: no space for [mem size
> 0x00200000 64bit pref]
> [ 1.085540] pci 0000:00:1c.3: BAR 15: failed to assign [mem size
> 0x00200000 64bit pref]
> [ 1.085613] pci 0000:00:1c.2: BAR 14: no space for [mem size 0x00200000]
> [ 1.085672] pci 0000:00:1c.2: BAR 14: failed to assign [mem size 0x00200000]
> [ 1.085738] pci 0000:00:1c.2: BAR 15: no space for [mem size
> 0x00200000 64bit pref]
> [ 1.085808] pci 0000:00:1c.2: BAR 15: failed to assign [mem size
> 0x00200000 64bit pref]
> [ 1.085884] pci 0000:00:1c.0: BAR 15: no space for [mem size
> 0x00200000 64bit pref]
> [ 1.085954] pci 0000:00:1c.0: BAR 15: failed to assign [mem size
> 0x00200000 64bit pref]
> [ 1.086026] pci 0000:00:1c.0: PCI bridge to [bus 01]
> [ 1.086083] pci 0000:00:1c.0: bridge window [io 0x1000-0x1fff]
> [ 1.086144] pci 0000:00:1c.0: bridge window [mem 0xd0400000-0xd07fffff]
The "no space" and "failed to assign" messages are all for bridge
windows (13 is the I/O window, 14 is the MMIO window, 15 is the MMIO
pref window). I can't tell if you have any devices below these
bridges (lspci would show them). If you don't have any devices below
these bridges, you can ignore the messages.
Bjorn
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-02-12 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 2:29 pcie: kernel log - BAR 15: no space for... BAR 15: failed to assign Muni Sekhar
2020-02-10 22:28 ` Bjorn Helgaas [this message]
2020-02-11 14:06 ` Muni Sekhar
2020-02-11 14:40 ` Bjorn Helgaas
2020-02-11 16:32 ` Muni Sekhar
2020-02-11 20:16 ` Bjorn Helgaas
2020-02-12 8:12 ` Muni Sekhar
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=20200210222834.GA74627@google.com \
--to=helgaas@kernel.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-pci@vger.kernel.org \
--cc=munisekharrms@gmail.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;
as well as URLs for NNTP newsgroup(s).