==System Environment== -------------------------- Regression: Yes. It's a igt bug. Good commit on igt: 75365eb01b7cb530426d84ea5357ed7b31575337 Bad commit on igt: d0a41b47ea5ed1ac5ca45f83d2917c6ad41b644a Non-working platforms: BSW ==kernel== -------------------------- origin/drm-intel-nightly: 257d90d13794c2eb545ab0d6c708f21e2a0378b6(fails) drm-intel-nightly: 2014y-08m-21d-10h-03m-09s integration manifest origin/drm-intel-next-queued: 3a5f87c286515c54ff5c52c3e64d0c522b7570c0(works) drm: fix plane rotation when restoring fbdev configuration origin/drm-intel-fixes: 1a125d8a2c22b11741fc47d4ffcf7a5ffa044dd3(works) drm/i915: don't try to retrain a DP link on an inactive CRTC ==Bug detailed description== igt/kms_render some subcases fail, and sometimes calltrace "WARNING: CPU: 3 PID: 5335 at drivers/gpu/drm/i915/intel_display.c:1066 chv_dpio_cmn_power_well_disable+0x63/0xc5 [i915]()" occurs. Case list: igt/kms_render/direct-render igt/kms_render/gpu-blit Output: [root@x-bsw01 tests]# ./kms_render --run-subtest direct-render IGT-Version: 1.7-g50166d2 (x86_64) (Linux: 3.17.0-rc1_drm-intel-nightly_257d90_20140825+ x86_64) Beginning test direct-render with 1920x1080 @ 60Hz / RGB565 on pipe C, encoder TMDS, connector HDMI-A Test direct-render with 1920x1080 @ 60Hz / RGB565 on pipe C, encoder TMDS, connector HDMI-A: SKIPPED Beginning test direct-render with 1920x1080 @ 60Hz / RGB888 on pipe C, encoder TMDS, connector HDMI-A Test assertion failure function igt_create_fb_with_bo_size, file igt_fb.c:427: Failed assertion: ret == 0 Last errno: 22, Invalid argument Subtest direct-render: FAIL [root@x-bsw01 tests]# dmesg -r|egrep ""<[1-4]>""|grep drm <4>[ 5400.002259] WARNING: CPU: 3 PID: 5335 at drivers/gpu/drm/i915/intel_display.c:1066 chv_dpio_cmn_power_well_disable+0x63/0xc5 [i915]() <4>[ 5400.002267] 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 snd_hda_intel snd_hda_controller pcspkr serio_raw snd_hda_codec snd_hwdep snd_pcm r8169 snd_timer snd soundcore battery ac option usb_wwan usbserial i915 button video drm_kms_helper drm cfbfillrect cfbimgblt cfbcopyarea <4>[ 5400.002318] CPU: 3 PID: 5335 Comm: kms_render Tainted: G W 3.17.0-rc1_drm-intel-nightly_257d90_20140825+ #1796 <4>[ 5400.002501] [<ffffffffa0058ddc>] ? drm_helper_probe_single_connector_modes_merge_bits+0xbc/0x31b [drm_kms_helper] <4>[ 5400.002520] [<ffffffffa001b26c>] ? drm_mode_getconnector+0xe4/0x2ff [drm] <4>[ 5400.002536] [<ffffffffa0023cd8>] ? drm_modeset_unlock_all+0x41/0x50 [drm] <4>[ 5400.002551] [<ffffffffa0010908>] ? drm_ioctl+0x279/0x3bc [drm] <4>[ 5400.002576] [<ffffffffa001b188>] ? drm_mode_getcrtc+0xb3/0xb3 [drm] ==Reproduce steps== ---------------------------- 1. ./kms_render --run-subtest direct-render
Created attachment 105406 [details] dmesg
This failure is able to reproduce on latest -nightly(4144c90b76dfe6eaa2205ac947090786b5091cff) on BDW root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./kms_render --run-subtest direct-render IGT-Version: 1.7-gf473a55 (x86_64) (Linux: 3.17.0-rc2_drm-intel-nightly_4144c9_20140904+ x86_64) Beginning test direct-render with 1920x1080 @ 60Hz / RGB565 on pipe A, encoder TMDS, connector eDP Test direct-render with 1920x1080 @ 60Hz / RGB565 on pipe A, encoder TMDS, connector eDP: PASSED Beginning test direct-render with 1920x1080 @ 40Hz / RGB888 on pipe A, encoder TMDS, connector eDP Test assertion failure function igt_create_fb_with_bo_size, file igt_fb.c:427: Failed assertion: ret == 0 Last errno: 22, Invalid argument Subtest direct-render: FAIL
commit 9df77d566409fcef90c7ea63bb6d3df8d8c76dde Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Sat Sep 6 12:08:13 2014 +0100 lib/igt_fb: Ignore RGB888 None of our display hardware supports the packed 24-bit format, so stop trying to use it and causing test failures. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=78873&list_id=465068 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Created attachment 106099 [details] dmesg The failure still able to reproduce on latest -nightly(99f444f7f8308ca93d56a3802a3e1a8abcad7f57) with latest igt() root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./kms_render --run-subtest direct-render IGT-Version: 1.8-g107151c (x86_64) (Linux: 3.17.0-rc4_drm-intel-nightly_99f444_20140910+ x86_64) Beginning test direct-render with 1920x1080 @ 60Hz / RGB565 on pipe A, encoder TMDS, connector eDP Test direct-render with 1920x1080 @ 60Hz / RGB565 on pipe A, encoder TMDS, connector eDP: PASSED Beginning test direct-render with 1920x1080 @ 40Hz / XRGB8888 on pipe A, encoder TMDS, connector eDP Test direct-render with 1920x1080 @ 40Hz / XRGB8888 on pipe A, encoder TMDS, connector eDP: PASSED Beginning test direct-render with @ 0Hz / XRGB2101010 on pipe A, encoder TMDS, connector eDP Test assertion failure function gem_create, file ioctl_wrappers.c:416: Failed assertion: drmIoctl((fd), ((((2U|1U) << (((0+8)+8)+14)) | ((('d')) << (0+8)) | (((0x40 + 0x1b)) << 0) | ((((sizeof(struct drm_i915_gem_create)))) << ((0+8)+8)))), (&create)) == 0 Last errno: 22, Invalid argument Subtest direct-render: FAIL (16.916s)
(In reply to comment #4) > Created attachment 106099 [details] > dmesg > > The failure still able to reproduce on latest > -nightly(99f444f7f8308ca93d56a3802a3e1a8abcad7f57) with latest igt() > > root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./kms_render > --run-subtest direct-render > IGT-Version: 1.8-g107151c (x86_64) (Linux: > 3.17.0-rc4_drm-intel-nightly_99f444_20140910+ x86_64) > Beginning test direct-render with 1920x1080 @ 60Hz / RGB565 on pipe A, > encoder TMDS, connector eDP > Test direct-render with 1920x1080 @ 60Hz / RGB565 on pipe A, encoder TMDS, > connector eDP: PASSED > Beginning test direct-render with 1920x1080 @ 40Hz / XRGB8888 on pipe A, > encoder TMDS, connector eDP > Test direct-render with 1920x1080 @ 40Hz / XRGB8888 on pipe A, encoder TMDS, > connector eDP: PASSED > Beginning test direct-render with @ 0Hz / XRGB2101010 on pipe A, encoder > TMDS, connector eDP > Test assertion failure function gem_create, file ioctl_wrappers.c:416: > Failed assertion: drmIoctl((fd), ((((2U|1U) << (((0+8)+8)+14)) | ((('d')) << > (0+8)) | (((0x40 + 0x1b)) << 0) | ((((sizeof(struct drm_i915_gem_create)))) > << ((0+8)+8)))), (&create)) == 0 > Last errno: 22, Invalid argument > Subtest direct-render: FAIL (16.916s) Update igt commit: 107151ce9f82955191a7fd6a2e6bfd5ff8cc5aea
You noticed that's a different bug... Wasn't a bug opened for the zero-sized mode and bo just yesterday?
(In reply to comment #5) > (In reply to comment #4) > > Created attachment 106099 [details] > > dmesg > > > > The failure still able to reproduce on latest > > -nightly(99f444f7f8308ca93d56a3802a3e1a8abcad7f57) with latest igt() > > > > root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./kms_render > > --run-subtest direct-render > > IGT-Version: 1.8-g107151c (x86_64) (Linux: > > 3.17.0-rc4_drm-intel-nightly_99f444_20140910+ x86_64) > > Beginning test direct-render with 1920x1080 @ 60Hz / RGB565 on pipe A, > > encoder TMDS, connector eDP > > Test direct-render with 1920x1080 @ 60Hz / RGB565 on pipe A, encoder TMDS, > > connector eDP: PASSED > > Beginning test direct-render with 1920x1080 @ 40Hz / XRGB8888 on pipe A, > > encoder TMDS, connector eDP > > Test direct-render with 1920x1080 @ 40Hz / XRGB8888 on pipe A, encoder TMDS, > > connector eDP: PASSED > > Beginning test direct-render with @ 0Hz / XRGB2101010 on pipe A, encoder > > TMDS, connector eDP > > Test assertion failure function gem_create, file ioctl_wrappers.c:416: > > Failed assertion: drmIoctl((fd), ((((2U|1U) << (((0+8)+8)+14)) | ((('d')) << > > (0+8)) | (((0x40 + 0x1b)) << 0) | ((((sizeof(struct drm_i915_gem_create)))) > > << ((0+8)+8)))), (&create)) == 0 > > Last errno: 22, Invalid argument > > Subtest direct-render: FAIL (16.916s) > > Update igt commit: 107151ce9f82955191a7fd6a2e6bfd5ff8cc5aea I reported new Bug 83788 for this failure. Verified this one.
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.