[Bug 110237] New: [CI][SHARDS] igt at gem_busy@close-race - fail - Failed assertion: !"GPU hung"

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Mar 25 09:45:49 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=110237

            Bug ID: 110237
           Summary: [CI][SHARDS] igt at gem_busy@close-race - fail - Failed
                    assertion: !"GPU hung"
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: lakshminarayana.vudum at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5792/shard-apl2/igt@gem_busy@close-race.html
Starting subtest: close-race
(gem_busy:2911) igt_aux-CRITICAL: Test assertion failure function sig_abort,
file ../lib/igt_aux.c:500:
(gem_busy:2911) igt_aux-CRITICAL: Failed assertion: !"GPU hung"
Subtest close-race failed.
**** DEBUG ****
(gem_busy:2911) drmtest-DEBUG: Test requirement passed: !(fd<0)
(gem_busy:2911) igt_dummyload-DEBUG: Test requirement passed:
vgem_has_fences(cork->vgem.device)
(gem_busy:2911) igt_debugfs-DEBUG: Opening debugfs directory
'/sys/kernel/debug/dri/0'
(gem_busy:2911) drmtest-DEBUG: Test requirement passed: !(fd<0)
(gem_busy:2911) igt_dummyload-DEBUG: Test requirement passed:
vgem_has_fences(cork->vgem.device)
(gem_busy:2911) igt_debugfs-DEBUG: Opening debugfs directory
'/sys/kernel/debug/dri/0'
(gem_busy:2911) drmtest-DEBUG: Test requirement passed: !(fd<0)
(gem_busy:2911) igt_dummyload-DEBUG: Test requirement passed:
vgem_has_fences(cork->vgem.device)
(gem_busy:2911) igt_debugfs-DEBUG: Opening debugfs directory
'/sys/kernel/debug/dri/0'
(gem_busy:2911) drmtest-DEBUG: Test requirement passed: !(fd<0)
(gem_busy:2911) igt_dummyload-DEBUG: Test requirement passed:
vgem_has_fences(cork->vgem.device)
(gem_busy:2911) igt_debugfs-DEBUG: Opening debugfs directory
'/sys/kernel/debug/dri/0'
(gem_busy:2911) DEBUG: Test requirement passed: ncpus > 1
(gem_busy:2911) igt_core-DEBUG: Test requirement passed:
!igt_run_in_simulation()
(gem_busy:2911) intel_os-DEBUG: Checking 38 surfaces of size 4096 bytes (total
176128) against RAM
(gem_busy:2911) drmtest-DEBUG: Test requirement passed: !(fd<0)
(gem_busy:2911) igt_debugfs-DEBUG: Opening debugfs directory
'/sys/kernel/debug/dri/0'
(gem_busy:2911) igt_debugfs-DEBUG: Opening debugfs directory
'/sys/kernel/debug/dri/0'
(gem_busy:2911) intel_os-DEBUG: Test requirement passed: sufficient_memory
(gem_busy:2911) DEBUG: Test requirement passed: nengine
(gem_busy:2911) igt_aux-CRITICAL: Test assertion failure function sig_abort,
file ../lib/igt_aux.c:500:
(gem_busy:2911) igt_aux-CRITICAL: Failed assertion: !"GPU hung"
(gem_busy:2911) igt_core-INFO: Stack trace:
(gem_busy:2911) igt_core-INFO:   #0 ../lib/igt_core.c:1474 __igt_fail_assert()
(gem_busy:2911) igt_core-INFO:   #1 ../lib/igt_aux.c:504
igt_fork_hang_detector()
(gem_busy:2911) igt_core-INFO:   #2 [killpg+0x40]
(gem_busy:2911) igt_core-INFO:   #3 ../sysdeps/unix/sysv/linux/wait.c:29 wait()
(gem_busy:2911) igt_core-INFO:   #4 ../lib/igt_core.c:1755 __igt_waitchildren()
(gem_busy:2911) igt_core-INFO:   #5 ../lib/igt_core.c:1806 igt_waitchildren()
(gem_busy:2911) igt_core-INFO:   #6 ../tests/i915/gem_busy.c:405 close_race()
(gem_busy:2911) igt_core-INFO:   #7 ../tests/i915/gem_busy.c:556
__real_main476()
(gem_busy:2911) igt_core-INFO:   #8 ../tests/i915/gem_busy.c:476 main()
(gem_busy:2911) igt_core-INFO:   #9 ../csu/libc-start.c:344 __libc_start_main()
(gem_busy:2911) igt_core-INFO:   #10 [_start+0x2a]
****  END  ****
Subtest close-race: FAIL (22.074s)
gem_busy: ../lib/igt_core.c:1530: igt_exit: Assertion `!num_test_children'
failed.
Received signal SIGABRT.
Stack trace: 
 #0 [fatal_sig_handler+0xd5]
 #1 [killpg+0x40]
 #2 [gsignal+0xc7]
 #3 [abort+0x141]
 #4 [uselocale+0x33a]
 #5 [__assert_fail+0x42]
 #6 [igt_exit+0x1e6]
 #7 [main+0x49]
 #8 [__libc_start_main+0xe7]
 #9 [_start+0x2a]

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190325/3ec054c8/attachment.html>


More information about the intel-gfx-bugs mailing list