Bug 86231

Summary: [BYT]igt/kms_sink_crc_basic Input/output error
Product: DRI Reporter: lu hua <huax.lu>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED NOTABUG QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg none

Description lu hua 2014-11-13 05:55:49 UTC 
Created attachment 109382 [details]
dmesg

==System Environment==
--------------------------
Regression: not sure

Non-working platforms: BYT

==kernel==
--------------------------
drm-intel-nightly/22ba72f728eaf30e63ded0c0bb0484b4bc6f92d4

==Bug detailed description==
Run this case, the return code is 77, So piglit's result is skip. Run it manually, output shows Input/output error.


IGT-Version: 1.8-g50d539e (x86_64) (Linux: 3.18.0-rc4_drm-intel-nightly_22ba72_20141113+ x86_64)
Test requirement not met in function get_crc, file kms_sink_crc_basic.c:59:
Test requirement: ret > 0
Last errno: 5, Input/output error

root@x-byt06:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# echo $?
77

==Reproduce steps==
---------------------------- 
1. ./kms_sink_crc_basic
Comment 1 Jesse Barnes 2015-04-02 17:22:07 UTC 
Looks like the test is behaving as expected, skipping if the sink crc file isn't available, so I think this is notabug.
Comment 2 ye.tian 2015-04-03 07:54:02 UTC 
I didn't find any error on the latest kernel and igt.

output:
---------------------
root@x-byt06:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./kms_sink_crc_basic
IGT-Version: 1.10-ge8457ed (x86_64) (Linux: 4.0.0-rc6_drm-intel-nightly_333cf6_20150403+ x86_64)
SUCCESS (0.225s)
root@x-byt06:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# echo $?
0
Comment 3 Elizabeth 2017-10-06 14:33:51 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.