[Bug 103514] New: [BAT] igt at gem_exec_nop@basic-parallel - Failed assertion: !"GPU hung"

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Oct 30 11:12:55 UTC 2017 

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

            Bug ID: 103514
           Summary: [BAT]  igt at gem_exec_nop@basic-parallel - 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: marta.lofstedt at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

CI_DRM_3293 fi-glk-dsi igt at gem_exec_nop@basic-parallel failed:

(gem_exec_nop:1922) igt-aux-CRITICAL: Test assertion failure function
sig_abort, file igt_aux.c:484:
(gem_exec_nop:1922) igt-aux-CRITICAL: Failed assertion: !"GPU hung"
Subtest basic-parallel failed.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3293/fi-glk-dsi/igt@gem_exec_nop@basic-parallel.html

NOTE: after this there are a bunch a spuriously skipped tests and then
fail on:        
(kms_pipe_crc_basic:2409) igt-gt-CRITICAL: Test assertion failure function
igt_force_gpu_reset, file igt_gt.c:406:
(kms_pipe_crc_basic:2409) igt-gt-CRITICAL: Failed assertion: !wedged
(kms_pipe_crc_basic:2409) igt-gt-CRITICAL: Last errno: 9, Bad file descriptor
Subtest hang-read-crc-pipe-B failed.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3293/fi-glk-dsi/igt@kms_pipe_crc_basic@hang-read-crc-pipe-a.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3293/fi-glk-dsi/igt@kms_pipe_crc_basic@hang-read-crc-pipe-b.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3293/fi-glk-dsi/igt@kms_pipe_crc_basic@hang-read-crc-pipe-c.html

and then there is a dmesg-warn on:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3293/fi-glk-dsi/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html

[  395.321772] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[  395.321921] WARN_ON(reset && reset != -19)
[  395.321959] ------------[ cut here ]------------
[  395.321995] WARNING: CPU: 2 PID: 2462 at
drivers/gpu/drm/i915/i915_gem.c:4725 i915_gem_sanitize+0x52/0x80 [i915]
[  395.321997] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek
snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp
crct10dif_pclmul crc32_pclmul i915 ghash_clmulni_intel snd_hda_intel
snd_hda_codec snd_hwdep snd_hda_core r8169 mii mei_me snd_pcm prime_numbers mei
i2c_hid pinctrl_geminilake pinctrl_intel
[  395.322070] CPU: 2 PID: 2462 Comm: kworker/u8:7 Tainted: G     U         
4.14.0-rc6-CI-CI_DRM_3293+ #1
[  395.322073] Hardware name: Intel Corp. Geminilake/GLK RVP2 LP4SD (07), BIOS
GELKRVPA.X64.0062.B30.1708222146 08/22/2017
[  395.322080] Workqueue: events_unbound async_run_entry_fn
[  395.322084] task: ffff88017807cec0 task.stack: ffffc90002194000
[  395.322117] RIP: 0010:i915_gem_sanitize+0x52/0x80 [i915]
[  395.322120] RSP: 0018:ffffc90002197c50 EFLAGS: 00010282
[  395.322124] RAX: 000000000000001e RBX: ffff880168480000 RCX:
0000000000000006
[  395.322126] RDX: 0000000000000006 RSI: ffffffff81d0e984 RDI:
ffffffff81cc2576
[  395.322130] RBP: ffffc90002197c60 R08: 0000000000000000 R09:
0000000000000001
[  395.322132] R10: 0000000000000000 R11: 0000000000000000 R12:
ffff880168480070
[  395.322134] R13: 0000000000000000 R14: 0000000000000000 R15:
ffffffff81cea5ef
[  395.322136] FS:  0000000000000000(0000) GS:ffff88017fd00000(0000)
knlGS:0000000000000000
[  395.322139] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  395.322141] CR2: 0000560453047068 CR3: 0000000174e85000 CR4:
00000000003406e0
[  395.322143] Call Trace:
[  395.322178]  i915_gem_suspend+0x111/0x170 [i915]
[  395.322208]  i915_drm_suspend+0x6d/0x170 [i915]
[  395.322238]  i915_pm_suspend+0x28/0x40 [i915]
[  395.322246]  pci_pm_suspend+0x78/0x140
[  395.322251]  dpm_run_callback+0x6f/0x310
[  395.322255]  ? pci_pm_freeze+0xf0/0xf0
[  395.322260]  __device_suspend+0x102/0x380
[  395.322264]  ? dpm_watchdog_set+0x70/0x70
[  395.322270]  async_suspend+0x1f/0xa0
[  395.322274]  async_run_entry_fn+0x38/0x160
[  395.322279]  process_one_work+0x221/0x650
[  395.322286]  worker_thread+0x4e/0x3b0
[  395.322292]  kthread+0x114/0x150
[  395.322294]  ? process_one_work+0x650/0x650
[  395.322297]  ? kthread_create_on_node+0x40/0x40
[  395.322303]  ret_from_fork+0x27/0x40
[  395.322311] Code: 5d c3 be ff ff ff ff 48 89 df e8 da dc 02 00 85 c0 74 ea
83 f8 ed 74 e5 48 c7 c6 c8 3a 23 a0 48 c7 c7 dc 0a 22 a0 e8 0f 51 fb e0 <0f> ff
eb ce 4c 8d 67 70 31 f6 4c 89 e7 e8 8c 00 7d e1 48 89 df 
[  395.322431] ---[ end trace 82f68684f9edfc24 ]---

Why are we having this inconsistent behavior when the GPU is wedged. Also, see
bug 102848. On the shards it would be very time consuming to find these
patterns.

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

More information about the intel-gfx-bugs mailing list