Created attachment 137073 [details] CFL-dmesg-kernel-logs CoffeeLake S UDIMM RVP QA system is failing with the following test: igt@gem_sync@preempt-all Running: IGT-Version: 1.21-g37bd27f (x86_64) (Linux: 4.15.0-drm-intel-qa-ww5-commit-5f9f363+ x86_64) Component: drm tag: libdrm-2.4.89-17-g1cc1774 commit: 1cc17744b988106b4fe71ee9d3d17b651d6adb40 Component: cairo tag: 1.15.8-76-g6b05938 commit: 6c675653b1cc325b78eb54dc3669ad207c653e2d Component: intel-gpu-tools tag: intel-gpu-tools-1.20-310-g37bd27f commit: 37bd27f28a868c287faf361864a16e77b8d9246f Component: piglit tag: piglit-v1 commit: 736496667329bf73a706aebec6f8287078df79ae grub_parameters="drm.debug=0x1e i915.alpha_support=1 intel_iommu=igfx_off log_buf_len=4M i915.enable_guc=-1 i915.guc_log_level=1 auto panic=1 nmi_watchdog=panic fsck.repair=yes i915.error_capture=yes" Ubuntu_16.10_64bit **** DEBUG **** (gem_sync:26386) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0' (gem_sync:26386) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0' (gem_sync:26386) igt-aux-CRITICAL: Test assertion failure function sig_abort, file igt_aux.c:482: (gem_sync:26386) igt-aux-CRITICAL: Failed assertion: !"GPU hung" (gem_sync:26386) igt-core-INFO: Stack trace: (gem_sync:26386) igt-core-INFO: #0 [__igt_fail_assert+0x101] (gem_sync:26386) igt-core-INFO: #1 [sig_abort+0x3a] (gem_sync:26386) igt-core-INFO: #2 [killpg+0x40] (gem_sync:26386) igt-core-INFO: #3 [__wait+0x1e] (gem_sync:26386) igt-core-INFO: #4 [igt_waitchildren+0x61] (gem_sync:26386) igt-core-INFO: #5 [igt_waitchildren_timeout+0xe] (gem_sync:26386) igt-core-INFO: #6 [preempt+0x2c2] (gem_sync:26386) igt-core-INFO: #7 [__real_main785+0x6cf] (gem_sync:26386) igt-core-INFO: #8 [main+0x27] (gem_sync:26386) igt-core-INFO: #9 [__libc_start_main+0xf1] (gem_sync:26386) igt-core-INFO: #10 [_start+0x2a] (gem_sync:26386) igt-core-INFO: #11 [<unknown>+0x2a] **** END ****
*** This bug has been marked as a duplicate of bug 104871 ***
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.