Created attachment 105728 [details] dmesg ==System Environment== -------------------------- Regression: No. This bug always exist Non-working platforms: BSW ==kernel== -------------------------- origin/drm-intel-nightly: 4144c90b76dfe6eaa2205ac947090786b5091cff(fails) drm-intel-nightly: 2014y-09m-03d-15h-44m-26s integration manifest origin/drm-intel-next-queued: 8fe8a3feeb5aedd17f7b09e51b60b38a6ba7005f(fails) drm/i915: init sprites with univeral plane init function origin/drm-intel-fixes: 77520c8fccc1a599ff7a7b786dacdfdad38b96e4(fails) drm/i915: Prevent recursive deadlock on releasing a busy userptr ==Bug detailed description== ----------------------------- igt/drv_module_reload fails and causes "[drm:i915_stolen_to_physical] *ERROR* conflict detected with stolen region: [0x7cf00000 - 0x7ef00000]" Output: [root@x-bsw01 tests]# ./drv_module_reload unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device ./drv_module_reload: line 27: 3860 Killed rmmod i915 WARNING: i915.ko still loaded! [root@x-bsw01 tests]# echo $? 1 [root@x-bsw01 tests]# dmesg -r|egrep ""<[1-4]>""|grep drm <3>[ 2.212221] [drm:i915_stolen_to_physical] *ERROR* conflict detected with stolen region: [0x7cf00000 - 0x7ef00000] <4>[ 189.533537] Modules linked in: ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables ipv6 dm_mod snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic serio_raw pcspkr snd_hda_controller snd_hda_codec snd_hwdep i2c_i801 snd_pcm snd_timer r8169 snd soundcore battery ac option usb_wwan usbserial i915(-) button video drm_kms_helper drm cfbfillrect cfbimgblt cfbcopyarea [last unloaded: snd_hda_intel] <4>[ 189.533612] CPU: 2 PID: 3860 Comm: rmmod Not tainted 3.17.0-rc2_drm-intel-nightly_4144c9_20140904+ #2116 <4>[ 189.533814] [<ffffffffa001aa7b>] ? drm_mode_config_cleanup+0x9b/0x23f [drm] <4>[ 189.533917] [<ffffffffa00133eb>] ? drm_dev_unregister+0x1e/0x8b [drm] <4>[ 189.533938] [<ffffffffa0013ccf>] ? drm_put_dev+0x45/0x4e [drm] <4>[ 189.534024] [<ffffffffa0015375>] ? drm_pci_exit+0x39/0x9c [drm] ==Reproduce steps== ---------------------------- 1. ./drv_module_reload
Can you attach the output of /proc/iomem on this machine?
Also, you don't see this at boot?
Oh nevermind... the module reload is failing
Probably something Ville can fix quickly.
The results are from a very old kernel. Please retest with something recent. The stolen mem error is normal since the BIOS is buggy.
(In reply to Ville Syrjala from comment #5) > The results are from a very old kernel. Please retest with something recent. > > The stolen mem error is normal since the BIOS is buggy. Test still fails on latest -nightly(bfdd01aa1825aa0068f9236b21362b550f6d630f) root@x-bsw01:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# dmesg -r|egrep "<[1-4]>"|grep drm <3>[ 2.251166] [drm:i915_gem_init_stolen [i915]] *ERROR* conflict detected with stolen region: [0x7ce00000 - 0x7ee00000] root@x-bsw01:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./drv_module_reload unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device module successfully unloaded modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open moddep file '/lib/modules/3.18.0-rc7_drm-intel-nightly_bfdd01_20141208+/modules.dep.bin' Killed root@x-bsw01:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# dmesg -r|egrep "<[1-4]>"|grep drm <3>[ 2.251166] [drm:i915_gem_init_stolen [i915]] *ERROR* conflict detected with stolen region: [0x7ce00000 - 0x7ee00000] <4>[ 128.816111] Modules linked in: dm_mod snd_hda_codec_hdmi iTCO_wdt iTCO_vendor_support snd_hda_codec_realtek snd_hda_codec_generic serio_raw pcspkr i2c_i801 lpc_ich mfd_core snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore battery ac acpi_cpufreq option usb_wwan usbserial button video cfbfillrect cfbimgblt cfbcopyarea [last unloaded: drm] <4>[ 128.816117] CPU: 1 PID: 4310 Comm: drv_module_relo Not tainted 3.18.0-rc7_drm-intel-nightly_bfdd01_20141208+ #2380 root@x-bsw01:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests#
Looks like the unload still failed (the "killed" line). Does it fail in the same place? Please attach the failing dmesg from the latest kernel when it fails. I'm assuming the failure is the same, but who knows.
This issue also happended on BYT.
(In reply to Ding Heng from comment #8) > This issue also happended on BYT. Heng, please attach your latest dmesg here.
Created attachment 112518 [details] dmesg on byt.
Looks to be working now: [root@jbarnes-byt tests]$ ./drv_module_reload unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device module successfully unloaded module successfully loaded again
(In reply to Jesse Barnes from comment #11) > Looks to be working now: > [root@jbarnes-byt tests]$ ./drv_module_reload > unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device > module successfully unloaded > module successfully loaded again ./drv_module_reload unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device rmmod: ERROR: Module i915 is in use WARNING: i915.ko still loaded!
Test it on the latest nightly kernel, this problem does not exists. output: ------------------ root@x-byt01:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./drv_module_reload unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device module successfully unloaded module successfully loaded again root@x-bsw03:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./drv_module_reload unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device module successfully unloaded module successfully loaded again
Closing Verified+Fixed.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.