* [PATCH] drm/i915: Show guilty context name on GPU reset
@ 2019-11-08 19:01 Chris Wilson
2019-11-08 19:01 ` [Intel-gfx] " Chris Wilson
` (3 more replies)
0 siblings, 4 replies; 8+ messages in thread
From: Chris Wilson @ 2019-11-08 19:01 UTC (permalink / raw)
To: intel-gfx
We mention that we are resetting the GPU, and dump the device state for
post mortem debugging. However, while that dump contains the active
processes and the one flagged as causing the error, we do not always
include that information in dmesg. Include the name of the guilty
process in dmesg for reference.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
drivers/gpu/drm/i915/gt/intel_reset.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/i915/gt/intel_reset.c b/drivers/gpu/drm/i915/gt/intel_reset.c
index f03e000051c1..86d52383bf9d 100644
--- a/drivers/gpu/drm/i915/gt/intel_reset.c
+++ b/drivers/gpu/drm/i915/gt/intel_reset.c
@@ -87,6 +87,10 @@ static bool context_mark_guilty(struct i915_gem_context *ctx)
if (!i915_gem_context_is_bannable(ctx))
return false;
+ dev_notice(ctx->i915->drm.dev,
+ "%s context reset due to GPU hang\n",
+ ctx->name);
+
/* Record the timestamp for the last N hangs */
prev_hang = ctx->hang_timestamp[0];
for (i = 0; i < ARRAY_SIZE(ctx->hang_timestamp) - 1; i++)
--
2.24.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 8+ messages in thread* [Intel-gfx] [PATCH] drm/i915: Show guilty context name on GPU reset
2019-11-08 19:01 [PATCH] drm/i915: Show guilty context name on GPU reset Chris Wilson
@ 2019-11-08 19:01 ` Chris Wilson
2019-11-08 19:50 ` ✓ Fi.CI.BAT: success for " Patchwork
` (2 subsequent siblings)
3 siblings, 0 replies; 8+ messages in thread
From: Chris Wilson @ 2019-11-08 19:01 UTC (permalink / raw)
To: intel-gfx
We mention that we are resetting the GPU, and dump the device state for
post mortem debugging. However, while that dump contains the active
processes and the one flagged as causing the error, we do not always
include that information in dmesg. Include the name of the guilty
process in dmesg for reference.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
drivers/gpu/drm/i915/gt/intel_reset.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/i915/gt/intel_reset.c b/drivers/gpu/drm/i915/gt/intel_reset.c
index f03e000051c1..86d52383bf9d 100644
--- a/drivers/gpu/drm/i915/gt/intel_reset.c
+++ b/drivers/gpu/drm/i915/gt/intel_reset.c
@@ -87,6 +87,10 @@ static bool context_mark_guilty(struct i915_gem_context *ctx)
if (!i915_gem_context_is_bannable(ctx))
return false;
+ dev_notice(ctx->i915->drm.dev,
+ "%s context reset due to GPU hang\n",
+ ctx->name);
+
/* Record the timestamp for the last N hangs */
prev_hang = ctx->hang_timestamp[0];
for (i = 0; i < ARRAY_SIZE(ctx->hang_timestamp) - 1; i++)
--
2.24.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 8+ messages in thread* ✓ Fi.CI.BAT: success for drm/i915: Show guilty context name on GPU reset
2019-11-08 19:01 [PATCH] drm/i915: Show guilty context name on GPU reset Chris Wilson
2019-11-08 19:01 ` [Intel-gfx] " Chris Wilson
@ 2019-11-08 19:50 ` Patchwork
2019-11-08 19:50 ` [Intel-gfx] " Patchwork
2019-11-10 15:59 ` ✓ Fi.CI.IGT: " Patchwork
2019-11-11 10:28 ` [PATCH] " Mika Kuoppala
3 siblings, 1 reply; 8+ messages in thread
From: Patchwork @ 2019-11-08 19:50 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915: Show guilty context name on GPU reset
URL : https://patchwork.freedesktop.org/series/69217/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7299 -> Patchwork_15198
====================================================
Summary
-------
**WARNING**
Minor unknown changes coming with Patchwork_15198 need to be verified
manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_15198, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_15198:
### IGT changes ###
#### Warnings ####
* igt@i915_pm_rpm@basic-rte:
- fi-kbl-guc: [SKIP][1] ([fdo#109271]) -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/fi-kbl-guc/igt@i915_pm_rpm@basic-rte.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/fi-kbl-guc/igt@i915_pm_rpm@basic-rte.html
Known issues
------------
Here are the changes found in Patchwork_15198 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_suspend@basic-s3:
- fi-cml-s: [PASS][3] -> [DMESG-WARN][4] ([fdo#111764])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/fi-cml-s/igt@gem_exec_suspend@basic-s3.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/fi-cml-s/igt@gem_exec_suspend@basic-s3.html
#### Possible fixes ####
* igt@i915_selftest@live_blt:
- fi-hsw-peppy: [DMESG-FAIL][5] ([fdo#112147]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/fi-hsw-peppy/igt@i915_selftest@live_blt.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/fi-hsw-peppy/igt@i915_selftest@live_blt.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][7] ([fdo#111407]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
[fdo#111764]: https://bugs.freedesktop.org/show_bug.cgi?id=111764
[fdo#112147]: https://bugs.freedesktop.org/show_bug.cgi?id=112147
Participating hosts (51 -> 45)
------------------------------
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7299 -> Patchwork_15198
CI-20190529: 20190529
CI_DRM_7299: e7de48a8b1161a99f4b8e4483bc1bb85f5d31039 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5268: c94958b8f7caefcda72392417ae6f3a98e36a48b @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_15198: e2084c7b34ecd15946bc604af96155eee91483ab @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
e2084c7b34ec drm/i915: Show guilty context name on GPU reset
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread* ✓ Fi.CI.IGT: success for drm/i915: Show guilty context name on GPU reset
2019-11-08 19:01 [PATCH] drm/i915: Show guilty context name on GPU reset Chris Wilson
2019-11-08 19:01 ` [Intel-gfx] " Chris Wilson
2019-11-08 19:50 ` ✓ Fi.CI.BAT: success for " Patchwork
@ 2019-11-10 15:59 ` Patchwork
2019-11-10 15:59 ` [Intel-gfx] " Patchwork
2019-11-11 10:28 ` [PATCH] " Mika Kuoppala
3 siblings, 1 reply; 8+ messages in thread
From: Patchwork @ 2019-11-10 15:59 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915: Show guilty context name on GPU reset
URL : https://patchwork.freedesktop.org/series/69217/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7299_full -> Patchwork_15198_full
====================================================
Summary
-------
**WARNING**
Minor unknown changes coming with Patchwork_15198_full need to be verified
manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_15198_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_15198_full:
### IGT changes ###
#### Warnings ####
* igt@i915_pm_dc@dc6-psr:
- shard-tglb: [SKIP][1] ([fdo#111865]) -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-tglb6/igt@i915_pm_dc@dc6-psr.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-tglb4/igt@i915_pm_dc@dc6-psr.html
Known issues
------------
Here are the changes found in Patchwork_15198_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_busy@close-race:
- shard-tglb: [PASS][3] -> [INCOMPLETE][4] ([fdo#111747])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-tglb3/igt@gem_busy@close-race.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-tglb6/igt@gem_busy@close-race.html
* igt@gem_ctx_exec@basic-invalid-context-vcs1:
- shard-iclb: [PASS][5] -> [SKIP][6] ([fdo#112080]) +10 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb2/igt@gem_ctx_exec@basic-invalid-context-vcs1.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb6/igt@gem_ctx_exec@basic-invalid-context-vcs1.html
* igt@gem_ctx_isolation@vcs1-reset:
- shard-iclb: [PASS][7] -> [SKIP][8] ([fdo#109276] / [fdo#112080]) +2 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb2/igt@gem_ctx_isolation@vcs1-reset.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb8/igt@gem_ctx_isolation@vcs1-reset.html
* igt@gem_ctx_shared@q-smoketest-all:
- shard-tglb: [PASS][9] -> [INCOMPLETE][10] ([fdo#111735])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-tglb1/igt@gem_ctx_shared@q-smoketest-all.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-tglb6/igt@gem_ctx_shared@q-smoketest-all.html
* igt@gem_ctx_switch@all-light:
- shard-tglb: [PASS][11] -> [INCOMPLETE][12] ([fdo#111672])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-tglb8/igt@gem_ctx_switch@all-light.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-tglb6/igt@gem_ctx_switch@all-light.html
* igt@gem_exec_balancer@smoke:
- shard-iclb: [PASS][13] -> [SKIP][14] ([fdo#110854])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb4/igt@gem_exec_balancer@smoke.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb5/igt@gem_exec_balancer@smoke.html
* igt@gem_exec_blt@dumb-buf-min:
- shard-tglb: [PASS][15] -> [INCOMPLETE][16] ([fdo#111736])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-tglb1/igt@gem_exec_blt@dumb-buf-min.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-tglb6/igt@gem_exec_blt@dumb-buf-min.html
* igt@gem_exec_schedule@fifo-bsd1:
- shard-iclb: [PASS][17] -> [SKIP][18] ([fdo#109276]) +10 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb2/igt@gem_exec_schedule@fifo-bsd1.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb6/igt@gem_exec_schedule@fifo-bsd1.html
* igt@gem_exec_schedule@wide-bsd:
- shard-iclb: [PASS][19] -> [SKIP][20] ([fdo#112146]) +5 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb8/igt@gem_exec_schedule@wide-bsd.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb4/igt@gem_exec_schedule@wide-bsd.html
* igt@gem_exec_suspend@basic-s4-devices:
- shard-tglb: [PASS][21] -> [INCOMPLETE][22] ([fdo#111850])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-tglb2/igt@gem_exec_suspend@basic-s4-devices.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-tglb4/igt@gem_exec_suspend@basic-s4-devices.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy:
- shard-snb: [PASS][23] -> [DMESG-WARN][24] ([fdo#110789] / [fdo#111870])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-snb4/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-snb5/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
* igt@gem_userptr_blits@sync-unmap-after-close:
- shard-snb: [PASS][25] -> [DMESG-WARN][26] ([fdo#111870])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-snb4/igt@gem_userptr_blits@sync-unmap-after-close.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-snb4/igt@gem_userptr_blits@sync-unmap-after-close.html
* igt@gem_workarounds@suspend-resume-context:
- shard-kbl: [PASS][27] -> [DMESG-WARN][28] ([fdo#108566])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-kbl2/igt@gem_workarounds@suspend-resume-context.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-kbl7/igt@gem_workarounds@suspend-resume-context.html
* igt@gem_workarounds@suspend-resume-fd:
- shard-tglb: [PASS][29] -> [INCOMPLETE][30] ([fdo#111832] / [fdo#111850]) +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-tglb8/igt@gem_workarounds@suspend-resume-fd.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-tglb5/igt@gem_workarounds@suspend-resume-fd.html
* igt@i915_selftest@live_hangcheck:
- shard-hsw: [PASS][31] -> [DMESG-FAIL][32] ([fdo#111991])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-hsw2/igt@i915_selftest@live_hangcheck.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-hsw5/igt@i915_selftest@live_hangcheck.html
* igt@i915_selftest@mock_requests:
- shard-glk: [PASS][33] -> [INCOMPLETE][34] ([fdo#103359] / [k.org#198133])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-glk7/igt@i915_selftest@mock_requests.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-glk6/igt@i915_selftest@mock_requests.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- shard-skl: [PASS][35] -> [FAIL][36] ([fdo#105363])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-skl8/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-skl6/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-msflip-blt:
- shard-tglb: [PASS][37] -> [FAIL][38] ([fdo#103167]) +3 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-tglb1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-msflip-blt.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-tglb6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-msflip-blt.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-wc:
- shard-iclb: [PASS][39] -> [FAIL][40] ([fdo#103167]) +5 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-wc.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb5/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-rte:
- shard-iclb: [PASS][41] -> [FAIL][42] ([fdo#103167] / [fdo#110378])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb1/igt@kms_frontbuffer_tracking@fbcpsr-1p-rte.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb4/igt@kms_frontbuffer_tracking@fbcpsr-1p-rte.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes:
- shard-apl: [PASS][43] -> [DMESG-WARN][44] ([fdo#108566]) +2 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-apl7/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-apl1/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [PASS][45] -> [SKIP][46] ([fdo#109642] / [fdo#111068])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb2/igt@kms_psr2_su@frontbuffer.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb6/igt@kms_psr2_su@frontbuffer.html
* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: [PASS][47] -> [SKIP][48] ([fdo#109441]) +2 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb6/igt@kms_psr@psr2_cursor_plane_move.html
* igt@kms_setmode@basic:
- shard-kbl: [PASS][49] -> [FAIL][50] ([fdo#99912])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-kbl2/igt@kms_setmode@basic.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-kbl2/igt@kms_setmode@basic.html
* igt@perf@oa-exponents:
- shard-glk: [PASS][51] -> [FAIL][52] ([fdo#105483])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-glk2/igt@perf@oa-exponents.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-glk7/igt@perf@oa-exponents.html
#### Possible fixes ####
* igt@gem_ctx_isolation@rcs0-s3:
- shard-apl: [DMESG-WARN][53] ([fdo#108566]) -> [PASS][54] +2 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-apl2/igt@gem_ctx_isolation@rcs0-s3.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-apl4/igt@gem_ctx_isolation@rcs0-s3.html
* igt@gem_ctx_persistence@vcs1-persistence:
- shard-iclb: [SKIP][55] ([fdo#109276] / [fdo#112080]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb8/igt@gem_ctx_persistence@vcs1-persistence.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb4/igt@gem_ctx_persistence@vcs1-persistence.html
* igt@gem_ctx_shared@exec-single-timeline-bsd:
- shard-iclb: [SKIP][57] ([fdo#110841]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb4/igt@gem_ctx_shared@exec-single-timeline-bsd.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb6/igt@gem_ctx_shared@exec-single-timeline-bsd.html
* igt@gem_ctx_shared@q-smoketest-vebox:
- shard-tglb: [INCOMPLETE][59] ([fdo#111735]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-tglb6/igt@gem_ctx_shared@q-smoketest-vebox.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-tglb4/igt@gem_ctx_shared@q-smoketest-vebox.html
* igt@gem_ctx_switch@vcs1:
- shard-iclb: [SKIP][61] ([fdo#112080]) -> [PASS][62] +4 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb5/igt@gem_ctx_switch@vcs1.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb2/igt@gem_ctx_switch@vcs1.html
* igt@gem_exec_schedule@preempt-queue-bsd1:
- shard-iclb: [SKIP][63] ([fdo#109276]) -> [PASS][64] +13 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb5/igt@gem_exec_schedule@preempt-queue-bsd1.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb4/igt@gem_exec_schedule@preempt-queue-bsd1.html
* igt@gem_exec_schedule@reorder-wide-bsd:
- shard-iclb: [SKIP][65] ([fdo#112146]) -> [PASS][66] +2 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb4/igt@gem_exec_schedule@reorder-wide-bsd.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb5/igt@gem_exec_schedule@reorder-wide-bsd.html
* igt@gem_exec_schedule@smoketest-all:
- shard-tglb: [INCOMPLETE][67] ([fdo#111855]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-tglb6/igt@gem_exec_schedule@smoketest-all.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-tglb1/igt@gem_exec_schedule@smoketest-all.html
* igt@gem_userptr_blits@sync-unmap-cycles:
- shard-snb: [DMESG-WARN][69] ([fdo#110789] / [fdo#111870]) -> [PASS][70]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-snb6/igt@gem_userptr_blits@sync-unmap-cycles.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-snb2/igt@gem_userptr_blits@sync-unmap-cycles.html
* igt@gem_workarounds@suspend-resume:
- shard-tglb: [INCOMPLETE][71] ([fdo#111832] / [fdo#111850]) -> [PASS][72] +3 similar issues
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-tglb7/igt@gem_workarounds@suspend-resume.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-tglb2/igt@gem_workarounds@suspend-resume.html
* igt@i915_selftest@live_requests:
- shard-tglb: [INCOMPLETE][73] ([fdo#112057]) -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-tglb2/igt@i915_selftest@live_requests.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-tglb4/igt@i915_selftest@live_requests.html
* igt@kms_color@pipe-b-ctm-0-5:
- shard-skl: [DMESG-WARN][75] ([fdo#106107]) -> [PASS][76]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-skl4/igt@kms_color@pipe-b-ctm-0-5.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-skl2/igt@kms_color@pipe-b-ctm-0-5.html
* igt@kms_cursor_legacy@cursor-vs-flip-atomic:
- shard-hsw: [FAIL][77] ([fdo#103355]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-hsw6/igt@kms_cursor_legacy@cursor-vs-flip-atomic.html
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-hsw6/igt@kms_cursor_legacy@cursor-vs-flip-atomic.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-skl: [FAIL][79] ([fdo#102670]) -> [PASS][80]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-skl7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-skl10/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-legacy:
- shard-apl: [DMESG-WARN][81] -> [PASS][82]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-apl6/igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-legacy.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-apl8/igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-legacy.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [DMESG-WARN][83] ([fdo#108566]) -> [PASS][84] +9 similar issues
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-kbl7/igt@kms_frontbuffer_tracking@fbc-suspend.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-suspend.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-render:
- shard-iclb: [FAIL][85] ([fdo#103167]) -> [PASS][86] +3 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb3/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-render.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb3/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-render.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-indfb-plflip-blt:
- shard-tglb: [FAIL][87] ([fdo#103167]) -> [PASS][88] +2 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-tglb2/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-indfb-plflip-blt.html
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-tglb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-indfb-plflip-blt.html
* igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min:
- shard-skl: [FAIL][89] ([fdo#108145]) -> [PASS][90] +1 similar issue
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-skl10/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-skl9/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html
* igt@kms_psr@psr2_sprite_render:
- shard-iclb: [SKIP][91] ([fdo#109441]) -> [PASS][92] +1 similar issue
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb5/igt@kms_psr@psr2_sprite_render.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb2/igt@kms_psr@psr2_sprite_render.html
* igt@kms_setmode@basic:
- shard-apl: [FAIL][93] ([fdo#99912]) -> [PASS][94]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-apl2/igt@kms_setmode@basic.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-apl4/igt@kms_setmode@basic.html
* igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend:
- shard-hsw: [INCOMPLETE][95] ([fdo#103540]) -> [PASS][96]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-hsw5/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-hsw2/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html
#### Warnings ####
* igt@gem_ctx_isolation@vcs1-nonpriv:
- shard-iclb: [FAIL][97] ([fdo#111329]) -> [SKIP][98] ([fdo#109276] / [fdo#112080])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb2/igt@gem_ctx_isolation@vcs1-nonpriv.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb6/igt@gem_ctx_isolation@vcs1-nonpriv.html
* igt@gem_eio@kms:
- shard-snb: [INCOMPLETE][99] ([fdo#105411]) -> [DMESG-WARN][100] ([fdo# 112000 ] / [fdo#111781])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-snb1/igt@gem_eio@kms.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-snb6/igt@gem_eio@kms.html
* igt@gem_mocs_settings@mocs-reset-bsd2:
- shard-iclb: [FAIL][101] ([fdo#111330]) -> [SKIP][102] ([fdo#109276]) +1 similar issue
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-iclb2/igt@gem_mocs_settings@mocs-reset-bsd2.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-iclb6/igt@gem_mocs_settings@mocs-reset-bsd2.html
* igt@gem_userptr_blits@dmabuf-unsync:
- shard-hsw: [DMESG-WARN][103] ([fdo#110789] / [fdo#111870]) -> [DMESG-WARN][104] ([fdo#111870])
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7299/shard-hsw5/igt@gem_userptr_blits@dmabuf-unsync.html
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/shard-hsw2/igt@gem_userptr_blits@dmabuf-unsync.html
* igt@gem_userptr_blits@sync-unmap:
- shard-hsw: [DMESG-WARN][105] ([fdo#111870]) -> [DMESG-WARN][106] ([fdo#110789] / [fdo#111870])
[105]: https://intel-gfx-ci.01.org/tree/
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15198/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH] drm/i915: Show guilty context name on GPU reset
2019-11-08 19:01 [PATCH] drm/i915: Show guilty context name on GPU reset Chris Wilson
` (2 preceding siblings ...)
2019-11-10 15:59 ` ✓ Fi.CI.IGT: " Patchwork
@ 2019-11-11 10:28 ` Mika Kuoppala
2019-11-11 10:28 ` [Intel-gfx] " Mika Kuoppala
3 siblings, 1 reply; 8+ messages in thread
From: Mika Kuoppala @ 2019-11-11 10:28 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
Chris Wilson <chris@chris-wilson.co.uk> writes:
> We mention that we are resetting the GPU, and dump the device state for
> post mortem debugging. However, while that dump contains the active
> processes and the one flagged as causing the error, we do not always
> include that information in dmesg. Include the name of the guilty
> process in dmesg for reference.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_reset.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_reset.c b/drivers/gpu/drm/i915/gt/intel_reset.c
> index f03e000051c1..86d52383bf9d 100644
> --- a/drivers/gpu/drm/i915/gt/intel_reset.c
> +++ b/drivers/gpu/drm/i915/gt/intel_reset.c
> @@ -87,6 +87,10 @@ static bool context_mark_guilty(struct i915_gem_context *ctx)
> if (!i915_gem_context_is_bannable(ctx))
> return false;
>
> + dev_notice(ctx->i915->drm.dev,
> + "%s context reset due to GPU hang\n",
> + ctx->name);
> +
> /* Record the timestamp for the last N hangs */
> prev_hang = ctx->hang_timestamp[0];
> for (i = 0; i < ARRAY_SIZE(ctx->hang_timestamp) - 1; i++)
> --
> 2.24.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [Intel-gfx] [PATCH] drm/i915: Show guilty context name on GPU reset
2019-11-11 10:28 ` [PATCH] " Mika Kuoppala
@ 2019-11-11 10:28 ` Mika Kuoppala
0 siblings, 0 replies; 8+ messages in thread
From: Mika Kuoppala @ 2019-11-11 10:28 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
Chris Wilson <chris@chris-wilson.co.uk> writes:
> We mention that we are resetting the GPU, and dump the device state for
> post mortem debugging. However, while that dump contains the active
> processes and the one flagged as causing the error, we do not always
> include that information in dmesg. Include the name of the guilty
> process in dmesg for reference.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_reset.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_reset.c b/drivers/gpu/drm/i915/gt/intel_reset.c
> index f03e000051c1..86d52383bf9d 100644
> --- a/drivers/gpu/drm/i915/gt/intel_reset.c
> +++ b/drivers/gpu/drm/i915/gt/intel_reset.c
> @@ -87,6 +87,10 @@ static bool context_mark_guilty(struct i915_gem_context *ctx)
> if (!i915_gem_context_is_bannable(ctx))
> return false;
>
> + dev_notice(ctx->i915->drm.dev,
> + "%s context reset due to GPU hang\n",
> + ctx->name);
> +
> /* Record the timestamp for the last N hangs */
> prev_hang = ctx->hang_timestamp[0];
> for (i = 0; i < ARRAY_SIZE(ctx->hang_timestamp) - 1; i++)
> --
> 2.24.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2019-11-11 10:28 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-11-08 19:01 [PATCH] drm/i915: Show guilty context name on GPU reset Chris Wilson
2019-11-08 19:01 ` [Intel-gfx] " Chris Wilson
2019-11-08 19:50 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-11-08 19:50 ` [Intel-gfx] " Patchwork
2019-11-10 15:59 ` ✓ Fi.CI.IGT: " Patchwork
2019-11-10 15:59 ` [Intel-gfx] " Patchwork
2019-11-11 10:28 ` [PATCH] " Mika Kuoppala
2019-11-11 10:28 ` [Intel-gfx] " Mika Kuoppala
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox