From: Laura Abbott <labbott@redhat.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Stephane Eranian <eranian@google.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
x86@kernel.org
Subject: Mapping multiple BARs with PNP (again)
Date: Wed, 13 May 2015 14:50:43 -0700 [thread overview]
Message-ID: <5553C733.5040000@redhat.com> (raw)
Hi,
We have some reports of warnings from ioremap about multiple
BARs:
[ 2.021722] resource sanity check: requesting [mem
0xfed10000-0xfed15fff], which spans more than reserved [mem
0xfed10000-0xfed13fff]
[ 2.021723] ------------[ cut here ]------------
[ 2.021727] WARNING: CPU: 1 PID: 1 at arch/x86/mm/ioremap.c:183
__ioremap_caller+0x258/0x2d0()
[ 2.021728] Info: mapping multiple BARs. Your kernel is fine.
[ 2.021729] Modules linked in:
[ 2.021733] CPU: 1 PID: 1 Comm: swapper/0 Not tainted
3.17.8-300.fc21.x86_64 #1
[ 2.021734] Hardware name: Hewlett-Packard HP ProBook 450 G0/1949,
BIOS 68IRF Ver. F.04 06/24/2013
[ 2.021735] 0000000000000000 00000000066e29d6 ffff880149a57b08
ffffffff81741aea
[ 2.021737] ffff880149a57b50 ffff880149a57b40 ffffffff810970bd
ffffc90000038000
[ 2.021739] 0000000000006000 00000000fed10000 8000000000000573
ffffc90000038000
[ 2.021741] Call Trace:
[ 2.021746] [<ffffffff81741aea>] dump_stack+0x45/0x56
[ 2.021749] [<ffffffff810970bd>] warn_slowpath_common+0x7d/0xa0
[ 2.021751] [<ffffffff8109713c>] warn_slowpath_fmt+0x5c/0x80
[ 2.021753] [<ffffffff8109d2a7>] ? iomem_map_sanity_check+0xc7/0xd0
[ 2.021755] [<ffffffff81061168>] __ioremap_caller+0x258/0x2d0
[ 2.021758] [<ffffffff810611f7>] ioremap_nocache+0x17/0x20
[ 2.021761] [<ffffffff81035d7c>] snb_uncore_imc_init_box+0x7c/0xc0
[ 2.021763] [<ffffffff81038e0c>] uncore_pci_probe+0xcc/0x1a0
[ 2.021766] [<ffffffff813c6ac5>] local_pci_probe+0x45/0xa0
[ 2.021769] [<ffffffff813c7f59>] pci_device_probe+0xf9/0x150
[ 2.021772] [<ffffffff8149a763>] driver_probe_device+0xa3/0x400
[ 2.021774] [<ffffffff8149ab8b>] __driver_attach+0x8b/0x90
[ 2.021775] [<ffffffff8149ab00>] ? __device_attach+0x40/0x40
[ 2.021777] [<ffffffff81498503>] bus_for_each_dev+0x73/0xc0
[ 2.021779] [<ffffffff8149a1fe>] driver_attach+0x1e/0x20
[ 2.021781] [<ffffffff81499dd0>] bus_add_driver+0x180/0x250
[ 2.021783] [<ffffffff81d560fa>] ? uncore_types_init+0x1a1/0x1a1
[ 2.021785] [<ffffffff8149b354>] driver_register+0x64/0xf0
[ 2.021787] [<ffffffff813c638c>] __pci_register_driver+0x4c/0x50
[ 2.021789] [<ffffffff81d5626e>] intel_uncore_init+0x174/0x410
[ 2.021791] [<ffffffff81d560fa>] ? uncore_types_init+0x1a1/0x1a1
[ 2.021794] [<ffffffff81002148>] do_one_initcall+0xd8/0x210
[ 2.021796] [<ffffffff810b4aad>] ? parse_args+0x21d/0x4e0
[ 2.021799] [<ffffffff81d491dd>] kernel_init_freeable+0x1b8/0x254
[ 2.021802] [<ffffffff817373b0>] ? rest_init+0x80/0x80
[ 2.021803] [<ffffffff817373be>] kernel_init+0xe/0xf0
[ 2.021807] [<ffffffff81748bfc>] ret_from_fork+0x7c/0xb0
[ 2.021808] [<ffffffff817373b0>] ? rest_init+0x80/0x80
[ 2.021813] ---[ end trace e33d153422839ba3 ]---
This looks like the issue fixed by
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=cb171f7abb9a
and I
believe this might have been specifically referenced by
https://lkml.org/lkml/2014/9/30/614 although that never got any
follow up. Does whatever BIOS this is need a workaround? Full
dmesg is at https://bugzilla.redhat.com/attachment.cgi?id=979268
Thanks,
Laura
reply other threads:[~2015-05-13 21:50 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=5553C733.5040000@redhat.com \
--to=labbott@redhat.com \
--cc=bhelgaas@google.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=x86@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 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.