From: Guilherme Malschitzky Schroeder <guilherme.m.schroeder@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.28-rc9 - ioremap.c:226 warning - GEM stuff?
Date: Fri, 19 Dec 2008 13:01:14 -0200 [thread overview]
Message-ID: <20081219130114.5fc87cfc.guilherme.m.schroeder@gmail.com> (raw)
Hi,
I'm running 2.6.28-rc9 on Debian sid/experimental with Xorg 1.5.3, intel driver 2.5.1 and i'm getting this warning in dmesg:
resource map sanity check conflict: 0xe0000000 0xefffffff 0xe0000000 0xe1feffff vesafb
------------[ cut here ]------------
WARNING: at arch/x86/mm/ioremap.c:226 __ioremap_caller+0xc8/0x2cd()
Modules linked in: kvm_intel kvm loop i2c_i801
Pid: 2101, comm: Xorg Not tainted 2.6.28-rc9 #10
Call Trace:
[<ffffffff8022be25>] warn_on_slowpath+0x51/0x75
[<ffffffff80230b5d>] iomem_map_sanity_check+0x75/0xac
[<ffffffff8021fba0>] __ioremap_caller+0xc8/0x2cd
[<ffffffff80360ffd>] i915_gem_entervt_ioctl+0x444/0x4d0
[<ffffffff80360ffd>] i915_gem_entervt_ioctl+0x444/0x4d0
[<ffffffff80360bb9>] i915_gem_entervt_ioctl+0x0/0x4d0
[<ffffffff803548e3>] drm_ioctl+0x1c9/0x253
[<ffffffff80280fc3>] vfs_ioctl+0x56/0x6c
[<ffffffff8028135e>] do_vfs_ioctl+0x385/0x3b2
[<ffffffff80276994>] vfs_write+0x121/0x136
[<ffffffff802813c8>] sys_ioctl+0x3d/0x5c
[<ffffffff8020b18b>] system_call_fastpath+0x16/0x1b
---[ end trace 05cd7e3729e479d6 ]---
Xorg:2101 conflicting memory types e0000000-f0000000 write-combining<->uncached-minus
reserve_memtype failed 0xe0000000-0xf0000000, track write-combining, req write-combining
Xorg:2101 conflicting memory types e0000000-f0000000 write-combining<->uncached-minus
reserve_memtype failed 0xe0000000-0xf0000000, track write-combining, req write-combining
I think is something related to GEM as my card supports it.
(II) intel(0): Integrated Graphics Chipset: Intel(R) Mobile Intel® GM45 Express Chipset
It's ok to just ignore?
If you need more info, let me know.
Thanks.
reply other threads:[~2008-12-19 15:01 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=20081219130114.5fc87cfc.guilherme.m.schroeder@gmail.com \
--to=guilherme.m.schroeder@gmail.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 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®