Summary: | [BSW]igt/kms_pipe_crc_basic some subcases timeout | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Guo Jinxian <jinxianx.guo> | ||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | normal | ||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||
Version: | unspecified | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Guo Jinxian
2014-09-05 07:08:12 UTC
Created attachment 105783 [details]
dmesg
It also happens on IVB/HSW. output: [root@x-hsw27 tests]# time ./kms_pipe_crc_basic --run-subtest hang-read-crc-pipe-B IGT-Version: 1.8-gab5f7ea (x86_64) (Linux: 3.18.0-rc2_drm-intel-fixes_7809a6_20141031+ x86_64) hang-read-crc-pipe-B: Testing connector VGA-1 using pipe B Subtest hang-read-crc-pipe-B: TIMEOUT (11.068s) ivb/hsw and bsw are completely different wrt pipe CRC. so let's restrict this to bsw and if there's still an issue on ibv/hsw please file a new bug report for that. (In reply to Daniel Vetter from comment #3) > ivb/hsw and bsw are completely different wrt pipe CRC. so let's restrict > this to bsw and if there's still an issue on ibv/hsw please file a new bug > report for that. Run binary on IVB/HSW, I am unable reproduce this issue, but automation testing, it still report timeout. File bug 88080 to track IVB/HSW. The timeout behaviour of the tests has been changed in commit cff102e (lib: use test failure status for igt_set_timeout). Please re-test with this commit. Test it on the latest nightly kernel and latest igt (e1ce5ea),this problem does not exist, but it fails. output: ------------------ root@x-bsw08:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# time ./kms_pipe_crc_basic --run-subtest hang-read-crc-pipe-C IGT-Version: 1.10-ge1ce5ea (x86_64) (Linux: 4.0.0_drm-intel-nightly_b9fe35_20150421+ x86_64) hang-read-crc-pipe-C: Testing connector eDP-1 using pipe C Timed out Subtest hang-read-crc-pipe-C failed. **** DEBUG **** Test requirement passed: !(pipe >= data->display.n_pipes) hang-read-crc-pipe-C: Testing connector eDP-1 using pipe C display: eDP-1: set_pipe(C) Clearing the fb with color (0.00,1.00,0.00) igt_create_fb_with_bo_size(width=1920, height=1080, format=0x34325258 [bpp=32], tiling=0x0, size=0 igt_create_fb_with_bo_size(handle=1, pitch=7680) display: C.0: plane_set_fb(51) display: commit { display: } Timed out **** END **** Subtest hang-read-crc-pipe-C: FAIL (10.891s) real 0m11.147s user 0m0.005s sys 0m0.055s (In reply to ye.tian from comment #6) > Test it on the latest nightly kernel and latest igt (e1ce5ea),this problem > does not exist, but it fails. > > output: > ------------------ > root@x-bsw08:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# time > ./kms_pipe_crc_basic --run-subtest hang-read-crc-pipe-C > IGT-Version: 1.10-ge1ce5ea (x86_64) (Linux: > 4.0.0_drm-intel-nightly_b9fe35_20150421+ x86_64) > hang-read-crc-pipe-C: Testing connector eDP-1 using pipe C > Timed out > Subtest hang-read-crc-pipe-C failed. > **** DEBUG **** > Test requirement passed: !(pipe >= data->display.n_pipes) > hang-read-crc-pipe-C: Testing connector eDP-1 using pipe C > display: eDP-1: set_pipe(C) > Clearing the fb with color (0.00,1.00,0.00) > igt_create_fb_with_bo_size(width=1920, height=1080, format=0x34325258 > [bpp=32], tiling=0x0, size=0 > igt_create_fb_with_bo_size(handle=1, pitch=7680) > display: C.0: plane_set_fb(51) > display: commit { > display: } > Timed out > **** END **** > Subtest hang-read-crc-pipe-C: FAIL (10.891s) > > real 0m11.147s > user 0m0.005s > sys 0m0.055s It may be the same as below bug: Bug 86767 - [BSW]igt/kms_rotation_crc subcases fail (In reply to ye.tian from comment #7) > It may be the same as below bug: > Bug 86767 - [BSW]igt/kms_rotation_crc subcases fail Yes, it looks like the same issue and since the kms_pipe_crc_basic subtests no longer timeout, this bug can be closed. Okay, verified it. 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.