From: "Éric Piel" <E.A.B.Piel@tudelft.nl>
To: Suresh Siddha <suresh.b.siddha@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: 2.6.28-rc4: Resource map sanity check conflict between vesafb and intel X driver?
Date: Tue, 18 Nov 2008 10:57:18 +0100 [thread overview]
Message-ID: <4922917E.8070201@tudelft.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 2242 bytes --]
Hello,
Booting a nearly 2.6.28-rc5 kernel, I got this warning which I never had
before (latest previous kernel being some 2.6.28-rc2).
resource map sanity check conflict: 0xd0000000 0xdfffffff 0xd0000000 0xd076ffff vesafb
------------[ cut here ]------------
WARNING: at arch/x86/mm/ioremap.c:226 __ioremap_caller+0x329/0x370()
Modules linked in: i915 drm usblp ipv6 microcode usbhid bluetooth binfmt_misc loop fuse cpufreq_conservative cpufreq_powersave acpi_cpufreq nvram hp_wmi af_packet rfkill_input snd_hda_intel snd_hwdep arc4 snd_seq_dummy ecb snd_seq_oss snd_seq_midi_event b43 snd_seq rfkill snd_seq_device rng_core snd_pcm_oss mac80211 sdhci_pci snd_pcm fan cfg80211 input_polldev ohci_hcd mmc_block snd_timer thermal ssb sdhci hp_accel processor tpm_infineon snd_page_alloc tpm ohci1394 yenta_socket rsrc_nonstatic pcmcia joydev serio_raw evdev sr_mod sg ehci_hcd iTCO_wdt ricoh_mmc mmc_core led_class snd_mixer_oss ieee1394 container video output tpm_bios uhci_hcd lis3lv02d wmi battery button e1000e pcmcia_core ac snd soundcore usbcore ext3 jbd [last unloaded: l2cap]
Pid: 3413, comm: X Not tainted 2.6.28-rc4-git-eric #39
Call Trace:
[<ffffffff8024515f>] warn_on_slowpath+0x5f/0x90
[<ffffffff8022e87a>] ? change_page_attr_set_clr+0xda/0x380
[<ffffffff8022ee82>] ? _set_memory_uc+0x22/0x30
[<ffffffff804ecec6>] ? _read_lock+0x16/0x30
[<ffffffff804ed141>] ? _read_unlock+0x11/0x40
[<ffffffff8022d689>] __ioremap_caller+0x329/0x370
[<ffffffffa04048fd>] ? i915_gem_entervt_ioctl+0x2fd/0x5d0 [i915]
[<ffffffff8022d816>] ioremap_wc+0x26/0x30
[<ffffffffa04048fd>] i915_gem_entervt_ioctl+0x2fd/0x5d0 [i915]
[<ffffffffa03e57ba>] drm_ioctl+0x10a/0x330 [drm]
[<ffffffffa0404600>] ? i915_gem_entervt_ioctl+0x0/0x5d0 [i915]
[<ffffffff802d690d>] vfs_ioctl+0x7d/0xa0
[<ffffffff802d69a4>] do_vfs_ioctl+0x74/0x470
[<ffffffff802d6dea>] sys_ioctl+0x4a/0x80
[<ffffffff8020c5ca>] system_call_fastpath+0x16/0x1b
---[ end trace f2aad082f0b30467 ]---
If I remove the vesafb driver, the warning goes away. That seems to be a
new warning. Probably is has always been happening on my laptop, how bad
is that? My X intel driver is 2.5.0 . If one driver has to be fixed, which
one: vesafb or intel?
Regards,
Eric
[-- Attachment #2: E_A_B_Piel.vcf --]
[-- Type: text/x-vcard, Size: 380 bytes --]
begin:vcard
fn;quoted-printable:=C3=89ric Piel
n;quoted-printable:Piel;=C3=89ric
org:Technical University of Delft;Software Engineering Research Group
adr:HB 08.080;;Mekelweg 4;Delft;;2628 CD;The Netherlands
email;internet:E.A.B.Piel@tudelft.nl
tel;work:+31 15 278 6338
tel;cell:+31 6 2437 9135
x-mozilla-html:FALSE
url:http://pieleric.free.fr
version:2.1
end:vcard
reply other threads:[~2008-11-18 10:18 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=4922917E.8070201@tudelft.nl \
--to=e.a.b.piel@tudelft.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox