From: Andi Kleen <andi@firstfloor.org>
To: venkatesh.pallipadi@intel.com, suresh.b.siddha@intel.com,
linux-kernel@vger.kernel.org
Subject: x86info results ioremap.c:226 __ioremap_caller+0xf2/0x2d6() WARNINGs
Date: Tue, 21 Oct 2008 10:36:15 +0200 [thread overview]
Message-ID: <20081021083615.GA4658@basil.nowhere.org> (raw)
When running x86info on a 2.6.27-git8 system I get
(the M taint is harmless in this case, came from other testing)
resource map sanity check conflict: 0x9e000 0x9efff 0x10000 0x9e7ff System RAM
------------[ cut here ]------------
WARNING: at /home/lsrc/linux/arch/x86/mm/ioremap.c:226 __ioremap_caller+0xf2/0x2d6()
Modules linked in:
Pid: 8805, comm: x86info Tainted: G M 2.6.27-git8 #110
Call Trace:
[<ffffffff80236ba1>] warn_on_slowpath+0x58/0x75
[<ffffffff8021db80>] ? do_flush_tlb_all+0x0/0x37
[<ffffffff8023b058>] ? on_each_cpu+0x21/0x2c
[<ffffffff8023bc80>] ? iomem_map_sanity_check+0x61/0x89
[<ffffffff8022467b>] __ioremap_caller+0xf2/0x2d6
[<ffffffff803c0648>] ? read_mem+0x5a/0xca
[<ffffffff802248e4>] xlate_dev_mem_ptr+0x73/0x9e
[<ffffffff803c0648>] read_mem+0x5a/0xca
[<ffffffff8028ed19>] vfs_read+0xab/0x134
[<ffffffff8028f01e>] sys_read+0x47/0x70
[<ffffffff8020b27b>] system_call_fastpath+0x16/0x1b
---[ end trace 8262d1d3f66bcc38 ]---
resource map sanity check conflict: 0x9e000 0x9efff 0x10000 0x9e7ff System RAM
------------[ cut here ]------------
WARNING: at /home/lsrc/linux/arch/x86/mm/ioremap.c:226 __ioremap_caller+0xf2/0x2d6()
Modules linked in:
Pid: 8805, comm: x86info Tainted: G M W 2.6.27-git8 #110
Call Trace:
[<ffffffff80236ba1>] warn_on_slowpath+0x58/0x75
[<ffffffff8021db80>] ? do_flush_tlb_all+0x0/0x37
[<ffffffff8023b058>] ? on_each_cpu+0x21/0x2c
[<ffffffff8023bc80>] ? iomem_map_sanity_check+0x61/0x89
[<ffffffff8022467b>] __ioremap_caller+0xf2/0x2d6
[<ffffffff803c0648>] ? read_mem+0x5a/0xca
[<ffffffff802248e4>] xlate_dev_mem_ptr+0x73/0x9e
[<ffffffff803c0648>] read_mem+0x5a/0xca
[<ffffffff8028ed19>] vfs_read+0xab/0x134
[<ffffffff8028f01e>] sys_read+0x47/0x70
[<ffffffff8020b27b>] system_call_fastpath+0x16/0x1b
---[ end trace 8262d1d3f66bcc38 ]---
resource map sanity check conflict: 0x9e000 0x9efff 0x10000 0x9e7ff System RAM
------------[ cut here ]------------
WARNING: at /home/lsrc/linux/arch/x86/mm/ioremap.c:226 __ioremap_caller+0xf2/0x2d6()
Modules linked in:
Pid: 9236, comm: x86info Tainted: G M W 2.6.27-git8 #110
Call Trace:
[<ffffffff80236ba1>] warn_on_slowpath+0x58/0x75
[<ffffffff8021db80>] ? do_flush_tlb_all+0x0/0x37
[<ffffffff8023b058>] ? on_each_cpu+0x21/0x2c
[<ffffffff8023bc80>] ? iomem_map_sanity_check+0x61/0x89
[<ffffffff8022467b>] __ioremap_caller+0xf2/0x2d6
[<ffffffff803c0648>] ? read_mem+0x5a/0xca
[<ffffffff802248e4>] xlate_dev_mem_ptr+0x73/0x9e
[<ffffffff803c0648>] read_mem+0x5a/0xca
[<ffffffff8028ed19>] vfs_read+0xab/0x134
[<ffffffff8028f01e>] sys_read+0x47/0x70
[<ffffffff8020b27b>] system_call_fastpath+0x16/0x1b
---[ end trace 8262d1d3f66bcc38 ]---
resource map sanity check conflict: 0x9e000 0x9efff 0x10000 0x9e7ff System RAM
... more of them ...
-Andi
--
ak@linux.intel.com
next reply other threads:[~2008-10-21 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 8:36 Andi Kleen [this message]
2008-10-23 20:56 ` x86info results ioremap.c:226 __ioremap_caller+0xf2/0x2d6() WARNINGs Suresh Siddha
2008-10-28 18:45 ` Suresh Siddha
2008-10-28 18:56 ` Ingo Molnar
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=20081021083615.GA4658@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.com \
--cc=venkatesh.pallipadi@intel.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 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.