Bug 108807

Summary: [CI][DRMTIP] igt@prime_busy@wait-hang-render- fail - Failed assertion: !prime_busy(&pfd[SCRATCH], true)
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: mwa <matthew.auld>
Status: RESOLVED MOVED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs, przanoni
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard: ReadyForDev
i915 platform: BXT, BYT, GLK, HSW, ICL, ILK, SNB i915 features: GEM/Other

Description Lakshmi 2018-11-20 12:55:55 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_145/fi-whl-u/igt@kms_color@pipe-c-ctm-negative.html

Out	
Starting subtest: pipe-C-ctm-negative
Stack trace:
  #0 ../lib/igt_core.c:1467 __igt_fail_assert()
  #1 ../tests/kms_color.c:1003 run_tests_for_pipe()
  #2 ../tests/kms_color.c:1171 __real_main1153()
  #3 ../tests/kms_color.c:1153 main()
  #4 ../csu/libc-start.c:344 __libc_start_main()
  #5 [_start+0x2a]
Subtest pipe-C-ctm-negative: FAIL (1.026s)
Test requirement not met in function run_tests_for_pipe, file ../tests/kms_color.c:849:
Test requirement: p < data->display.n_pipes
Last errno: 9, Bad file descriptor
Test requirement not met in function run_tests_for_pipe, file ../tests/kms_color.c:849:
Test requirement: p < data->display.n_pipes
Last errno: 9, Bad file descriptor
Test requirement not met in function run_tests_for_pipe, file ../tests/kms_color.c:849:
Test requirement: p < data->display.n_pipes
Last errno: 9, Bad file descriptor

Err	
Starting subtest: pipe-C-ctm-negative
(kms_color:2390) CRITICAL: Test assertion failure function run_tests_for_pipe, file ../tests/kms_color.c:1013:
(kms_color:2390) CRITICAL: Failed assertion: test_pipe_ctm(data, primary, red_green_blue, all_black, ctm)
Subtest pipe-C-ctm-negative failed.
**** DEBUG ****
(kms_color:2390) igt_kms-DEBUG: display: eDP-1: set_pipe(C)
(kms_color:2390) igt_kms-DEBUG: display: eDP-1: Selecting pipe C
(kms_color:2390) igt_fb-DEBUG: igt_create_fb_with_bo_size(width=3840, height=2160, format=0x34325258, tiling=0x0, size=0)
(kms_color:2390) igt_fb-DEBUG: igt_create_fb_with_bo_size(handle=1, pitch=15360)
(kms_color:2390) ioctl_wrappers-DEBUG: Test requirement passed: igt_has_fb_modifiers(fd)
(kms_color:2390) igt_fb-DEBUG: igt_create_fb_with_bo_size(width=3840, height=2160, format=0x34325258, tiling=0x0, size=0)
(kms_color:2390) igt_fb-DEBUG: igt_create_fb_with_bo_size(handle=2, pitch=15360)
(kms_color:2390) ioctl_wrappers-DEBUG: Test requirement passed: igt_has_fb_modifiers(fd)
(kms_color:2390) igt_kms-DEBUG: display: C.0: plane_set_fb(114)
(kms_color:2390) igt_kms-DEBUG: display: C.0: plane_set_size (3840x2160)
(kms_color:2390) igt_kms-DEBUG: display: C.0: fb_set_position(0,0)
(kms_color:2390) igt_kms-DEBUG: display: C.0: fb_set_size(3840x2160)
(kms_color:2390) igt_kms-DEBUG: display: commit {
(kms_color:2390) igt_kms-DEBUG: display:     eDP-1: SetCrtc pipe C, fb 114, src (0, 0), mode 3840x2160
(kms_color:2390) igt_kms-DEBUG: display: }
(kms_color:2390) igt_fb-DEBUG: Test requirement passed: cairo_surface_status(fb->cairo_surface) == CAIRO_STATUS_SUCCESS
(kms_color:2390) igt_kms-DEBUG: display: C.0: plane_set_fb(111)
(kms_color:2390) igt_kms-DEBUG: display: C.0: plane_set_size (3840x2160)
(kms_color:2390) igt_kms-DEBUG: display: C.0: fb_set_position(0,0)
(kms_color:2390) igt_kms-DEBUG: display: C.0: fb_set_size(3840x2160)
(kms_color:2390) igt_kms-DEBUG: display: commit {
(kms_color:2390) igt_kms-DEBUG: display:     eDP-1: SetCrtc pipe C, fb 111, src (0, 0), mode 3840x2160
(kms_color:2390) igt_kms-DEBUG: display: }
(kms_color:2390) igt_fb-DEBUG: Test requirement passed: cairo_surface_status(fb->cairo_surface) == CAIRO_STATUS_SUCCESS
(kms_color:2390) igt_kms-DEBUG: display: C.0: plane_set_fb(111)
(kms_color:2390) igt_kms-DEBUG: display: C.0: plane_set_size (3840x2160)
(kms_color:2390) igt_kms-DEBUG: display: C.0: fb_set_position(0,0)
(kms_color:2390) igt_kms-DEBUG: display: C.0: fb_set_size(3840x2160)
(kms_color:2390) igt_kms-DEBUG: display: commit {
(kms_color:2390) igt_kms-DEBUG: display:     eDP-1: SetCrtc pipe C, fb 111, src (0, 0), mode 3840x2160
(kms_color:2390) igt_kms-DEBUG: display: }
(kms_color:2390) igt_kms-DEBUG: display: C.0: plane_set_fb(0)
(kms_color:2390) igt_kms-DEBUG: display: C.0: plane_set_size (0x0)
(kms_color:2390) igt_kms-DEBUG: display: C.0: fb_set_position(0,0)
(kms_color:2390) igt_kms-DEBUG: display: C.0: fb_set_size(0x0)
(kms_color:2390) igt_kms-DEBUG: display: eDP-1: set_pipe(None)
(kms_color:2390) igt_kms-DEBUG: display: eDP-1: Selecting pipe None
(kms_color:2390) CRITICAL: Test assertion failure function run_tests_for_pipe, file ../tests/kms_color.c:1013:
(kms_color:2390) CRITICAL: Failed assertion: test_pipe_ctm(data, primary, red_green_blue, all_black, ctm)
(kms_color:2390) igt_core-INFO: Stack trace:
(kms_color:2390) igt_core-INFO:   #0 ../lib/igt_core.c:1467 __igt_fail_assert()
(kms_color:2390) igt_core-INFO:   #1 ../tests/kms_color.c:1003 run_tests_for_pipe()
(kms_color:2390) igt_core-INFO:   #2 ../tests/kms_color.c:1171 __real_main1153()
(kms_color:2390) igt_core-INFO:   #3 ../tests/kms_color.c:1153 main()
(kms_color:2390) igt_core-INFO:   #4 ../csu/libc-start.c:344 __libc_start_main()
(kms_color:2390) igt_core-INFO:   #5 [_start+0x2a]
****  END  ****
Subtest pipe-C-ctm-negative: FAIL (1.026s)
Comment 1 Chris Wilson 2018-11-20 13:02:01 UTC
Make up your mind about what you want to report.
Comment 2 Lakshmi 2018-11-20 13:10:12 UTC
(In reply to Chris Wilson from comment #1)
> Make up your mind about what you want to report.

Sorry..I copied wrong one

Starting subtest: wait-hang-render
Stack trace:
  #0 ../lib/igt_core.c:1467 __igt_fail_assert()
  #1 ../tests/prime_busy.c:164 busy()
  #2 ../tests/prime_busy.c:204 test_engine_mode()
  #3 ../tests/prime_busy.c:243 __real_main218()
  #4 ../tests/prime_busy.c:218 main()
  #5 ../csu/libc-start.c:344 __libc_start_main()
  #6 [_start+0x2a]
Subtest wait-hang-render: FAIL (13.816s)
Test requirement not met in function gem_require_ring, file ../lib/ioctl_wrappers.c:1486:
Test requirement: gem_has_ring(fd, ring)
Test requirement not met in function gem_require_ring, file ../lib/ioctl_wrappers.c:1486:
Test requirement: gem_has_ring(fd, ring)
Test requirement not met in function gem_require_ring, file ../lib/ioctl_wrappers.c:1486:
Test requirement: gem_has_ring(fd, ring)
Test requirement not met in function gem_require_ring, file ../lib/ioctl_wrappers.c:1486:
Test requirement: gem_has_ring(fd, ring)
Test requirement not met in function gem_require_ring, file ../lib/ioctl_wrappers.c:1486:
Test requirement: gem_has_ring(fd, ring)
Test requirement not met in function gem_require_ring, file ../lib/ioctl_wrappers.c:1486:
Test requirement: gem_has_ring(fd, ring)
Err	
Starting subtest: wait-hang-render
(prime_busy:2433) CRITICAL: Test assertion failure function busy, file ../tests/prime_busy.c:162:
(prime_busy:2433) CRITICAL: Failed assertion: !prime_busy(&pfd[SCRATCH], true)
Subtest wait-hang-render failed.
**** DEBUG ****
(prime_busy:2433) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(prime_busy:2433) DEBUG: Test requirement passed: __gem_execbuf(fd, &execbuf) == 0
(prime_busy:2433) CRITICAL: Test assertion failure function busy, file ../tests/prime_busy.c:162:
(prime_busy:2433) CRITICAL: Failed assertion: !prime_busy(&pfd[SCRATCH], true)
(prime_busy:2433) igt_core-INFO: Stack trace:
(prime_busy:2433) igt_core-INFO:   #0 ../lib/igt_core.c:1467 __igt_fail_assert()
(prime_busy:2433) igt_core-INFO:   #1 ../tests/prime_busy.c:164 busy()
(prime_busy:2433) igt_core-INFO:   #2 ../tests/prime_busy.c:204 test_engine_mode()
(prime_busy:2433) igt_core-INFO:   #3 ../tests/prime_busy.c:243 __real_main218()
(prime_busy:2433) igt_core-INFO:   #4 ../tests/prime_busy.c:218 main()
(prime_busy:2433) igt_core-INFO:   #5 ../csu/libc-start.c:344 __libc_start_main()
(prime_busy:2433) igt_core-INFO:   #6 [_start+0x2a]
****  END  ****
Subtest wait-hang-render: FAIL (13.816s)
Comment 4 Chris Wilson 2018-11-20 14:39:53 UTC
Pretty sure it goes wrong at the sync_file level -- but I don't think we check the equivalent gem_busy hang in CI at all.
Comment 5 Martin Peres 2018-12-28 14:17:00 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5345/shard-apl7/igt@prime_busy@hang-bsd.html

Starting subtest: hang-bsd
(prime_busy:2348) CRITICAL: Test assertion failure function busy, file ../tests/prime_busy.c:162:
(prime_busy:2348) CRITICAL: Failed assertion: !prime_busy(&pfd[SCRATCH], true)
Subtest hang-bsd failed.
Comment 6 Paulo Zanoni 2019-01-17 18:35:05 UTC
Can't reproduce this on my GLK machine after 500 runs. This might be dependent on results of previous tests. I'll keep trying.
Comment 7 Jani Saarinen 2019-01-17 20:18:57 UTC
Try to see what is sharded test list when issue occurs. So in this case use tests on this list eg. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5345/shard-apl7/run0.log and generate list or get that from IGT_4754 and shards list.
Comment 8 CI Bug Log 2019-01-28 10:54:38 UTC
A CI Bug Log filter associated to this bug has been updated:

{- APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) -}
{+ HSW APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) +}

 No new failures caught with the new filter
Comment 9 CI Bug Log 2019-01-28 11:02:35 UTC
A CI Bug Log filter associated to this bug has been updated:

{- HSW APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) -}
{+ HSW APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) +}

New failures caught by the filter:

* https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4791/shard-hsw8/igt@prime_busy@hang-blt.html
Comment 10 CI Bug Log 2019-01-28 11:03:29 UTC
A CI Bug Log filter associated to this bug has been updated:

{- HSW APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) -}
{+ HSW APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) +}

 No new failures caught with the new filter
Comment 11 CI Bug Log 2019-01-29 14:40:50 UTC
A CI Bug Log filter associated to this bug has been updated:

{- HSW APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) -}
{+ SNB SNBm HSW APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) +}

New failures caught by the filter:

* https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5500/shard-snb6/igt@prime_busy@hang-blt.html
Comment 12 CI Bug Log 2019-02-07 15:42:44 UTC
A CI Bug Log filter associated to this bug has been updated:

{- SNB SNBm HSW APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) -}
{+ SNB SNBm BYT HSW APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) +}

New failures caught by the filter:

* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_203/fi-byt-j1900/igt@prime_busy@hang-blt.html
Comment 13 CI Bug Log 2019-02-08 10:14:43 UTC
A CI Bug Log filter associated to this bug has been updated:

{- SNB SNBm BYT HSW APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) -}
{+ ILK SNB SNBm BYT HSW APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) +}

New failures caught by the filter:

* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_206/fi-ilk-650/igt@prime_busy@hang-render.html
Comment 14 CI Bug Log 2019-03-12 16:31:41 UTC
A CI Bug Log filter associated to this bug has been updated:

{- ILK SNB SNBm BYT HSW APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) -}
{+ ILK SNB BYT HSW APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) +}

 No new failures caught with the new filter
Comment 15 CI Bug Log 2019-05-15 07:24:14 UTC
A CI Bug Log filter associated to this bug has been updated:

{- ILK SNB BYT HSW APL GLK: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) -}
{+ ILK SNB BYT HSW APL GLK ICL: igt@prime_busy@(wait-)?hang-* - fail - Failed assertion: !prime_busy(&amp;pfd[SCRATCH], true) +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_285/fi-icl-y/igt@prime_busy@hang-vebox.html
Comment 16 Daniel Vetter 2019-05-16 13:08:08 UTC
Martin says we always blow up on the !prime_busy logic, so I guess first debug step would be a test patch to expand the race window (in case there is one) with a pile of sleeps and see what happens. Otherwise not much ideas, test seems to be doing the right things from a quick look.
Comment 17 Martin Peres 2019-11-29 17:59:43 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/187.

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.