Bug 83788 - [BDW Regression]igt/kms_render/direct-render fails
Summary: [BDW Regression]igt/kms_render/direct-render fails
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: high normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-12 06:29 UTC by Guo Jinxian
Modified: 2017-10-06 14:35 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (110.10 KB, text/plain)
2014-09-12 06:29 UTC, Guo Jinxian
no flags Details

Description Guo Jinxian 2014-09-12 06:29:58 UTC
Created attachment 106165 [details]
dmesg

==System Environment==
--------------------------
Regression: Yes.
Good commit on igt: d0a41b47ea5ed1ac5ca45f83d2917c6ad41b644a(bug 83220)
Bad commit on igt: 62f4d56676468cc6b7e1fb900ccf120d68352f65

Non-working platforms: BDW

==kernel==
--------------------------
origin/drm-intel-nightly: 907d7b0519abe7b8eac453089decfe0fc5049171(fails)
    drm-intel-nightly: 2014y-09m-11d-17h-29m-25s integration manifest
origin/drm-intel-next-queued:d04d1a15d828d5c89c45886db5ae01eed83349cc(fails)
    drm/i915: Extend BIOS stolen mem handling to all platform
origin/drm-intel-fixes: 7a98948f3b536ca9a077e84966ddc0e9f53726df(works)
    drm/i915: Wait for vblank before enabling the TV encoder

==Bug detailed description==
-----------------------------
igt/kms_render/direct-render fails


Output:
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_907d7b_20140912+ 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.872s)

==Reproduce steps==
---------------------------- 
1. ./kms_render --run-subtest direct-render
Comment 1 Chris Wilson 2014-09-12 08:13:12 UTC
commit f81d8eba4fb4448e6ea777aa2072c3b9f277e7cb
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Sep 12 09:11:55 2014 +0100

    igt/kms_render: Iterate only through the formats
    
    When testing each format, iterate through the formats and not randomly
    through the modes.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=83788
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Comment 2 Guo Jinxian 2014-09-15 02:03:22 UTC
Verified on latest -nightly(43df30da20447e2856b2761215ff274886a9f931) with latest igt(137877f16b7d026fa1bc17797604e17de2af7e92)

root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./kms_render --run-subtest direct-render
IGT-Version: 1.8-g137877f (x86_64) (Linux: 3.17.0-rc4_drm-intel-nightly_43df30_20140914+ 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 @ 60Hz / XRGB8888 on pipe A, encoder TMDS, connector eDP
Test direct-render with 1920x1080 @ 60Hz / XRGB8888 on pipe A, encoder TMDS, connector eDP: PASSED
Beginning test direct-render with 1920x1080 @ 60Hz / XRGB2101010 on pipe A, encoder TMDS, connector eDP
Test direct-render with 1920x1080 @ 60Hz / XRGB2101010 on pipe A, encoder TMDS, connector eDP: PASSED
Beginning test direct-render with 1920x1080 @ 60Hz / ARGB8888 on pipe A, encoder TMDS, connector eDP
Test direct-render with 1920x1080 @ 60Hz / ARGB8888 on pipe A, encoder TMDS, connector eDP: PASSED
Beginning test direct-render with 1920x1080 @ 60Hz / RGB565 on pipe B, encoder TMDS, connector eDP
Test direct-render with 1920x1080 @ 60Hz / RGB565 on pipe B, encoder TMDS, connector eDP: PASSED
Beginning test direct-render with 1920x1080 @ 60Hz / XRGB8888 on pipe B, encoder TMDS, connector eDP
Test direct-render with 1920x1080 @ 60Hz / XRGB8888 on pipe B, encoder TMDS, connector eDP: PASSED
Beginning test direct-render with 1920x1080 @ 60Hz / XRGB2101010 on pipe B, encoder TMDS, connector eDP
Test direct-render with 1920x1080 @ 60Hz / XRGB2101010 on pipe B, encoder TMDS, connector eDP: PASSED
Beginning test direct-render with 1920x1080 @ 60Hz / ARGB8888 on pipe B, encoder TMDS, connector eDP
Test direct-render with 1920x1080 @ 60Hz / ARGB8888 on pipe B, encoder TMDS, connector eDP: PASSED
Beginning test direct-render with 1920x1080 @ 60Hz / RGB565 on pipe C, encoder TMDS, connector eDP
Test direct-render with 1920x1080 @ 60Hz / RGB565 on pipe C, encoder TMDS, connector eDP: PASSED
Beginning test direct-render with 1920x1080 @ 60Hz / XRGB8888 on pipe C, encoder TMDS, connector eDP
Test direct-render with 1920x1080 @ 60Hz / XRGB8888 on pipe C, encoder TMDS, connector eDP: PASSED
Beginning test direct-render with 1920x1080 @ 60Hz / XRGB2101010 on pipe C, encoder TMDS, connector eDP
Test direct-render with 1920x1080 @ 60Hz / XRGB2101010 on pipe C, encoder TMDS, connector eDP: PASSED
Beginning test direct-render with 1920x1080 @ 60Hz / ARGB8888 on pipe C, encoder TMDS, connector eDP
Test direct-render with 1920x1080 @ 60Hz / ARGB8888 on pipe C, encoder TMDS, connector eDP: PASSED
Subtest direct-render: SUCCESS (99.009s)
root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# echo $?
0
Comment 3 Elizabeth 2017-10-06 14:35:45 UTC
Closing old verified.


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.