From: Ferry Toth <fntoth@gmail.com>
To: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: resource sanity check, mapping multiple BARs
Date: Mon, 6 Dec 2021 21:56:55 +0100 [thread overview]
Message-ID: <a19ca757-195d-c2d3-c1b8-529c1028a37f@gmail.com> (raw)
Hi,
Between v5.15 and v5.16-rc the following (unrelated?) errors are
appearing in kernel.log:
resource sanity check: requesting [mem 0xff200000-0xff3fffff], which
spans more than 0000:00:0e.0 [mem 0xff298000-0xff29bfff]
caller devm_ioremap+0x45/0x80 mapping multiple BARs
pmd_set_huge: Cannot satisfy [mem 0x05e00000-0x06000000] with a
huge-page mapping due to MTRR override.
This is on Intel Edison (Merrifield), which has (from lspci):
00:0e.0 System peripheral: Intel Corporation Device 119b (rev 01)
Flags: fast devsel, IRQ 25
Memory at ff298000 (32-bit, non-prefetchable) [size=16K]
Memory at ff2a2000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [b0] Power Management version 3
Capabilities: [b8] Vendor Specific Information: Len=08 <?>
Capabilities: [c0] PCI-X non-bridge device
Capabilities: [100] Vendor Specific Information: ID=0000 Rev=0
Len=024 <?>
Any suggestions on the cause of this would be welcome.
Ferry
reply other threads:[~2021-12-06 20:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a19ca757-195d-c2d3-c1b8-529c1028a37f@gmail.com \
--to=fntoth@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®