From: Douglas Gilbert <dgilbert@interlog.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Linux 4.4: warning ioremap.c:198
Date: Tue, 12 Jan 2016 02:19:29 +0100 [thread overview]
Message-ID: <569454A1.9030005@interlog.com> (raw)
Just noticed the warning shown below in lk 4.4 . Checked my previous
kernel which was lk 4.3.3 and it gets the warning as well. The machine
is a Lenovo X240 laptop.
Doug Gilbert
...
resource sanity check: requesting [mem 0xfed10000-0xfed15fff], which spans more
than pnp 00:01 [mem 0xfed10000-0xfed13fff]
------------[ cut here ]------------
WARNING: CPU: 2 PID: 1 at arch/x86/mm/ioremap.c:198 __ioremap_caller+0x205/0x360()
Info: mapping multiple BARs. Your kernel is fine.
Modules linked in:
CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.4.0 #243
Hardware name: LENOVO 20ALCTO1WW/20ALCTO1WW, BIOS GIET75WW (2.25 ) 06/24/2014
ffffffff817fbf6b ffff880119963ba0 ffffffff813151dc ffff880119963be8
ffff880119963bd8 ffffffff81055f76 ffffc90000068000 ffffc90000068000
00000000fed10000 0000000000000000 ffff8800c9d10fc0 ffff880119963c38
Call Trace:
[<ffffffff813151dc>] dump_stack+0x4e/0x82
[<ffffffff81055f76>] warn_slowpath_common+0x86/0xc0
[<ffffffff81055ffc>] warn_slowpath_fmt+0x4c/0x50
[<ffffffff8105d1c7>] ? iomem_map_sanity_check+0x97/0xd0
[<ffffffff81045c85>] __ioremap_caller+0x205/0x360
[<ffffffff81045df7>] ioremap_nocache+0x17/0x20
[<ffffffff8102665d>] snb_uncore_imc_init_box+0x6d/0x90
[<ffffffff81024cd5>] uncore_pci_probe+0xc5/0x1d0
[<ffffffff81352cfc>] pci_device_probe+0x8c/0x100
[<ffffffff81404d9b>] driver_probe_device+0x1fb/0x310
[<ffffffff81404f38>] __driver_attach+0x88/0x90
[<ffffffff81404eb0>] ? driver_probe_device+0x310/0x310
[<ffffffff81402de6>] bus_for_each_dev+0x66/0xa0
[<ffffffff814047fe>] driver_attach+0x1e/0x20
[<ffffffff81404418>] bus_add_driver+0x1b8/0x230
[<ffffffff819b8c23>] ? uncore_types_exit+0x26/0x26
[<ffffffff81405ba0>] driver_register+0x60/0xe0
[<ffffffff813514cd>] __pci_register_driver+0x5d/0x60
[<ffffffff819b8d05>] intel_uncore_init+0xe2/0x2d1
[<ffffffff819b8c23>] ? uncore_types_exit+0x26/0x26
[<ffffffff810003c9>] do_one_initcall+0x99/0x1e0
[<ffffffff819ae08e>] kernel_init_freeable+0x1ac/0x236
[<ffffffff81611ac0>] ? rest_init+0x140/0x140
[<ffffffff81611ace>] kernel_init+0xe/0xe0
[<ffffffff8161b1bf>] ret_from_fork+0x3f/0x70
[<ffffffff81611ac0>] ? rest_init+0x140/0x140
---[ end trace c7054f9c46af802f ]---
reply other threads:[~2016-01-12 1:19 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=569454A1.9030005@interlog.com \
--to=dgilbert@interlog.com \
--cc=linux-kernel@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 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.