* [RFC PATCH] drm/i915/debugfs: Only wedge if we have reset available
@ 2019-10-02 12:48 Janusz Krzysztofik
2019-10-02 15:45 ` Tvrtko Ursulin
` (4 more replies)
0 siblings, 5 replies; 7+ messages in thread
From: Janusz Krzysztofik @ 2019-10-02 12:48 UTC (permalink / raw)
To: Petri Latvala; +Cc: intel-gfx
If we process DROP_RESET_ACTIVE and cancel all outstanding requests by
forcing a GPU reset on a hardware with reset capabilities disabled or
not supported, we certainly end up with a terminally wedged GPU,
impossible to recover. That's probably not what we want.
Before setting the GPU wedged, verify if we have GPU reset available
and fail with -EBUSY if not.
Suggested-by: Petri Latvala <petri.latvala@intel.com>
Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: Michał Wajdeczko <michal.wajdeczko@intel.com>
Cc: Michał Winiarski <michal.winiarski@intel.com>
Cc: Piotr Piórkowski <piotr.piorkowski@intel.com>
Cc: Tomasz Lis <tomasz.lis@intel.com>
Cc: Petri Latvala <petri.latvala@intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: Martin Peres <martin.peres@linux.intel.com>
---
drivers/gpu/drm/i915/i915_debugfs.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
index fec9fb7cc384..0774ca6e2a05 100644
--- a/drivers/gpu/drm/i915/i915_debugfs.c
+++ b/drivers/gpu/drm/i915/i915_debugfs.c
@@ -3627,8 +3627,17 @@ i915_drop_caches_set(void *data, u64 val)
if (val & DROP_RESET_ACTIVE &&
wait_for(intel_engines_are_idle(&i915->gt),
- I915_IDLE_ENGINES_TIMEOUT))
+ I915_IDLE_ENGINES_TIMEOUT)) {
+ /*
+ * Only wedge if reset is supported and not disabled, otherwise
+ * we certainly end up with the GPU terminally wedged. Inform
+ * userspace about the problem instead.
+ */
+ if (!intel_has_gpu_reset(&i915->gt))
+ return -EBUSY;
+
intel_gt_set_wedged(&i915->gt);
+ }
/* No need to check and wait for gpu resets, only libdrm auto-restarts
* on ioctls on -EAGAIN. */
--
2.21.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 7+ messages in thread
* Re: [RFC PATCH] drm/i915/debugfs: Only wedge if we have reset available
2019-10-02 12:48 [RFC PATCH] drm/i915/debugfs: Only wedge if we have reset available Janusz Krzysztofik
@ 2019-10-02 15:45 ` Tvrtko Ursulin
2019-10-02 15:59 ` Chris Wilson
2019-10-02 16:33 ` [Intel-gfx] " kbuild test robot
` (3 subsequent siblings)
4 siblings, 1 reply; 7+ messages in thread
From: Tvrtko Ursulin @ 2019-10-02 15:45 UTC (permalink / raw)
To: Janusz Krzysztofik, Petri Latvala; +Cc: intel-gfx
On 02/10/2019 13:48, Janusz Krzysztofik wrote:
> If we process DROP_RESET_ACTIVE and cancel all outstanding requests by
> forcing a GPU reset on a hardware with reset capabilities disabled or
> not supported, we certainly end up with a terminally wedged GPU,
> impossible to recover. That's probably not what we want.
I forgot the whole background story here I'm afraid. Is the concern here
the IGT exit handler calling DROP_RESET_ACTIVE? If so with this patch it
will fail with -EBUSY, which could be fine, but what happens from the
perspective of next test which gets to run? It won't find a wedged GPU,
but will encounter a possibly nondeterministic amount of GPU work
scheduled before it, no?
Regards,
Tvrtko
> Before setting the GPU wedged, verify if we have GPU reset available
> and fail with -EBUSY if not.
>
> Suggested-by: Petri Latvala <petri.latvala@intel.com>
> Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
> Cc: Michał Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Michał Winiarski <michal.winiarski@intel.com>
> Cc: Piotr Piórkowski <piotr.piorkowski@intel.com>
> Cc: Tomasz Lis <tomasz.lis@intel.com>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Martin Peres <martin.peres@linux.intel.com>
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index fec9fb7cc384..0774ca6e2a05 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -3627,8 +3627,17 @@ i915_drop_caches_set(void *data, u64 val)
>
> if (val & DROP_RESET_ACTIVE &&
> wait_for(intel_engines_are_idle(&i915->gt),
> - I915_IDLE_ENGINES_TIMEOUT))
> + I915_IDLE_ENGINES_TIMEOUT)) {
> + /*
> + * Only wedge if reset is supported and not disabled, otherwise
> + * we certainly end up with the GPU terminally wedged. Inform
> + * userspace about the problem instead.
> + */
> + if (!intel_has_gpu_reset(&i915->gt))
> + return -EBUSY;
> +
> intel_gt_set_wedged(&i915->gt);
> + }
>
> /* No need to check and wait for gpu resets, only libdrm auto-restarts
> * on ioctls on -EAGAIN. */
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [RFC PATCH] drm/i915/debugfs: Only wedge if we have reset available
2019-10-02 15:45 ` Tvrtko Ursulin
@ 2019-10-02 15:59 ` Chris Wilson
0 siblings, 0 replies; 7+ messages in thread
From: Chris Wilson @ 2019-10-02 15:59 UTC (permalink / raw)
To: Janusz Krzysztofik, Petri Latvala, Tvrtko Ursulin; +Cc: intel-gfx
Quoting Tvrtko Ursulin (2019-10-02 16:45:18)
>
> On 02/10/2019 13:48, Janusz Krzysztofik wrote:
> > If we process DROP_RESET_ACTIVE and cancel all outstanding requests by
> > forcing a GPU reset on a hardware with reset capabilities disabled or
> > not supported, we certainly end up with a terminally wedged GPU,
> > impossible to recover. That's probably not what we want.
>
> I forgot the whole background story here I'm afraid. Is the concern here
> the IGT exit handler calling DROP_RESET_ACTIVE? If so with this patch it
> will fail with -EBUSY, which could be fine, but what happens from the
> perspective of next test which gets to run? It won't find a wedged GPU,
> but will encounter a possibly nondeterministic amount of GPU work
> scheduled before it, no?
Yes, that is the conundrum. If the test left work outstanding, and in a
few cases, we explicitly rely on the reset here to cancel persistent
(unbound nonpreemptible spinners) work, then it will cause the next
test, where drm_driver_open(DRM_INTEL) calls gem_quiescent_gpu(),
to wait until eventually it is wedged. There's a good chance that next
test will then fail because it doesn't handle the wedged gpu.
The alternative would be to wedge here, taint and reboot. Then
hopefully resume testing at the next test with vanilla state.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Intel-gfx] [RFC PATCH] drm/i915/debugfs: Only wedge if we have reset available
2019-10-02 12:48 [RFC PATCH] drm/i915/debugfs: Only wedge if we have reset available Janusz Krzysztofik
2019-10-02 15:45 ` Tvrtko Ursulin
@ 2019-10-02 16:33 ` kbuild test robot
2019-10-02 17:00 ` ✓ Fi.CI.BAT: success for " Patchwork
` (2 subsequent siblings)
4 siblings, 0 replies; 7+ messages in thread
From: kbuild test robot @ 2019-10-02 16:33 UTC (permalink / raw)
To: kbuild-all
[-- Attachment #1: Type: text/plain, Size: 5224 bytes --]
Hi Janusz,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on drm-intel/for-linux-next]
[cannot apply to v5.4-rc1 next-20191002]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Janusz-Krzysztofik/drm-i915-debugfs-Only-wedge-if-we-have-reset-available/20191002-235155
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-13) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/gpu/drm/i915/i915_debugfs.c: In function 'i915_drop_caches_set':
>> drivers/gpu/drm/i915/i915_debugfs.c:3618:28: error: passing argument 1 of 'intel_has_gpu_reset' from incompatible pointer type [-Werror=incompatible-pointer-types]
if (!intel_has_gpu_reset(&i915->gt))
^
In file included from drivers/gpu/drm/i915/i915_gem_gtt.h:45:0,
from drivers/gpu/drm/i915/i915_vma.h:33,
from drivers/gpu/drm/i915/gt/uc/intel_guc.h:17,
from drivers/gpu/drm/i915/gt/uc/intel_uc.h:9,
from drivers/gpu/drm/i915/gt/intel_gt_types.h:16,
from drivers/gpu/drm/i915/i915_drv.h:80,
from drivers/gpu/drm/i915/display/intel_display_types.h:46,
from drivers/gpu/drm/i915/i915_debugfs.c:35:
drivers/gpu/drm/i915/gt/intel_reset.h:74:6: note: expected 'struct drm_i915_private *' but argument is of type 'struct intel_gt *'
bool intel_has_gpu_reset(struct drm_i915_private *i915);
^~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/intel_has_gpu_reset +3618 drivers/gpu/drm/i915/i915_debugfs.c
3601
3602 static int
3603 i915_drop_caches_set(void *data, u64 val)
3604 {
3605 struct drm_i915_private *i915 = data;
3606
3607 DRM_DEBUG("Dropping caches: 0x%08llx [0x%08llx]\n",
3608 val, val & DROP_ALL);
3609
3610 if (val & DROP_RESET_ACTIVE &&
3611 wait_for(intel_engines_are_idle(&i915->gt),
3612 I915_IDLE_ENGINES_TIMEOUT)) {
3613 /*
3614 * Only wedge if reset is supported and not disabled, otherwise
3615 * we certainly end up with the GPU terminally wedged. Inform
3616 * userspace about the problem instead.
3617 */
> 3618 if (!intel_has_gpu_reset(&i915->gt))
3619 return -EBUSY;
3620
3621 intel_gt_set_wedged(&i915->gt);
3622 }
3623
3624 /* No need to check and wait for gpu resets, only libdrm auto-restarts
3625 * on ioctls on -EAGAIN. */
3626 if (val & (DROP_ACTIVE | DROP_IDLE | DROP_RETIRE | DROP_RESET_SEQNO)) {
3627 int ret;
3628
3629 ret = mutex_lock_interruptible(&i915->drm.struct_mutex);
3630 if (ret)
3631 return ret;
3632
3633 /*
3634 * To finish the flush of the idle_worker, we must complete
3635 * the switch-to-kernel-context, which requires a double
3636 * pass through wait_for_idle: first queues the switch,
3637 * second waits for the switch.
3638 */
3639 if (ret == 0 && val & (DROP_IDLE | DROP_ACTIVE))
3640 ret = i915_gem_wait_for_idle(i915,
3641 I915_WAIT_INTERRUPTIBLE |
3642 I915_WAIT_LOCKED,
3643 MAX_SCHEDULE_TIMEOUT);
3644
3645 if (ret == 0 && val & DROP_IDLE)
3646 ret = i915_gem_wait_for_idle(i915,
3647 I915_WAIT_INTERRUPTIBLE |
3648 I915_WAIT_LOCKED,
3649 MAX_SCHEDULE_TIMEOUT);
3650
3651 if (val & DROP_RETIRE)
3652 i915_retire_requests(i915);
3653
3654 mutex_unlock(&i915->drm.struct_mutex);
3655
3656 if (ret == 0 && val & DROP_IDLE)
3657 ret = intel_gt_pm_wait_for_idle(&i915->gt);
3658 }
3659
3660 if (val & DROP_RESET_ACTIVE && intel_gt_terminally_wedged(&i915->gt))
3661 intel_gt_handle_error(&i915->gt, ALL_ENGINES, 0, NULL);
3662
3663 fs_reclaim_acquire(GFP_KERNEL);
3664 if (val & DROP_BOUND)
3665 i915_gem_shrink(i915, LONG_MAX, NULL, I915_SHRINK_BOUND);
3666
3667 if (val & DROP_UNBOUND)
3668 i915_gem_shrink(i915, LONG_MAX, NULL, I915_SHRINK_UNBOUND);
3669
3670 if (val & DROP_SHRINK_ALL)
3671 i915_gem_shrink_all(i915);
3672 fs_reclaim_release(GFP_KERNEL);
3673
3674 if (val & DROP_IDLE) {
3675 flush_delayed_work(&i915->gem.retire_work);
3676 flush_work(&i915->gem.idle_work);
3677 }
3678
3679 if (val & DROP_FREED)
3680 i915_gem_drain_freed_objects(i915);
3681
3682 return 0;
3683 }
3684
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 70198 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* ✓ Fi.CI.BAT: success for drm/i915/debugfs: Only wedge if we have reset available
2019-10-02 12:48 [RFC PATCH] drm/i915/debugfs: Only wedge if we have reset available Janusz Krzysztofik
2019-10-02 15:45 ` Tvrtko Ursulin
2019-10-02 16:33 ` [Intel-gfx] " kbuild test robot
@ 2019-10-02 17:00 ` Patchwork
2019-10-02 17:31 ` [Intel-gfx] [RFC PATCH] " kbuild test robot
2019-10-03 1:07 ` ✓ Fi.CI.IGT: success for " Patchwork
4 siblings, 0 replies; 7+ messages in thread
From: Patchwork @ 2019-10-02 17:00 UTC (permalink / raw)
To: Janusz Krzysztofik; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/debugfs: Only wedge if we have reset available
URL : https://patchwork.freedesktop.org/series/67492/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6991 -> Patchwork_14628
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/index.html
Known issues
------------
Here are the changes found in Patchwork_14628 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- fi-blb-e6850: [PASS][1] -> [INCOMPLETE][2] ([fdo#107718])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/fi-blb-e6850/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/fi-blb-e6850/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
* igt@prime_vgem@basic-wait-default:
- fi-icl-u3: [PASS][3] -> [DMESG-WARN][4] ([fdo#107724]) +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/fi-icl-u3/igt@prime_vgem@basic-wait-default.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/fi-icl-u3/igt@prime_vgem@basic-wait-default.html
#### Possible fixes ####
* igt@gem_mmap_gtt@basic-small-bo-tiledx:
- fi-icl-u3: [DMESG-WARN][5] ([fdo#107724]) -> [PASS][6] +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/fi-icl-u3/igt@gem_mmap_gtt@basic-small-bo-tiledx.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/fi-icl-u3/igt@gem_mmap_gtt@basic-small-bo-tiledx.html
* igt@i915_selftest@live_requests:
- {fi-tgl-u}: [INCOMPLETE][7] ([fdo#111867]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/fi-tgl-u/igt@i915_selftest@live_requests.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/fi-tgl-u/igt@i915_selftest@live_requests.html
* igt@kms_chamelium@hdmi-crc-fast:
- fi-icl-u2: [FAIL][9] ([fdo#109635 ]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/fi-icl-u2/igt@kms_chamelium@hdmi-crc-fast.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/fi-icl-u2/igt@kms_chamelium@hdmi-crc-fast.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-icl-u2: [FAIL][11] ([fdo#109483]) -> [PASS][12] +1 similar issue
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/fi-icl-u2/igt@kms_chamelium@hdmi-hpd-fast.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/fi-icl-u2/igt@kms_chamelium@hdmi-hpd-fast.html
#### Warnings ####
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][13] ([fdo#111045] / [fdo#111096]) -> [FAIL][14] ([fdo#111407])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#109483]: https://bugs.freedesktop.org/show_bug.cgi?id=109483
[fdo#109635 ]: https://bugs.freedesktop.org/show_bug.cgi?id=109635
[fdo#111045]: https://bugs.freedesktop.org/show_bug.cgi?id=111045
[fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
[fdo#111678]: https://bugs.freedesktop.org/show_bug.cgi?id=111678
[fdo#111850]: https://bugs.freedesktop.org/show_bug.cgi?id=111850
[fdo#111867]: https://bugs.freedesktop.org/show_bug.cgi?id=111867
Participating hosts (51 -> 45)
------------------------------
Additional (1): fi-kbl-soraka
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-bsw-n3050 fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_6991 -> Patchwork_14628
CI-20190529: 20190529
CI_DRM_6991: 1f02b477cc08d4560a0c2cf6cc98340e09c7c734 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5209: ec639c89860b859fdf4b038c2fa8ad593bd6909e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_14628: 4445d40108bea3af6359252de635ce25010c132d @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
4445d40108be drm/i915/debugfs: Only wedge if we have reset available
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Intel-gfx] [RFC PATCH] drm/i915/debugfs: Only wedge if we have reset available
2019-10-02 12:48 [RFC PATCH] drm/i915/debugfs: Only wedge if we have reset available Janusz Krzysztofik
` (2 preceding siblings ...)
2019-10-02 17:00 ` ✓ Fi.CI.BAT: success for " Patchwork
@ 2019-10-02 17:31 ` kbuild test robot
2019-10-03 1:07 ` ✓ Fi.CI.IGT: success for " Patchwork
4 siblings, 0 replies; 7+ messages in thread
From: kbuild test robot @ 2019-10-02 17:31 UTC (permalink / raw)
To: kbuild-all
[-- Attachment #1: Type: text/plain, Size: 9311 bytes --]
Hi Janusz,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on drm-intel/for-linux-next]
[cannot apply to v5.4-rc1 next-20191002]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Janusz-Krzysztofik/drm-i915-debugfs-Only-wedge-if-we-have-reset-available/20191002-235155
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: i386-randconfig-g001-201939 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-13) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from include/linux/export.h:45:0,
from include/linux/linkage.h:7,
from include/linux/kernel.h:8,
from include/linux/sched/mm.h:5,
from drivers/gpu/drm/i915/i915_debugfs.c:29:
drivers/gpu/drm/i915/i915_debugfs.c: In function 'i915_drop_caches_set':
drivers/gpu/drm/i915/i915_debugfs.c:3618:28: error: passing argument 1 of 'intel_has_gpu_reset' from incompatible pointer type [-Werror=incompatible-pointer-types]
if (!intel_has_gpu_reset(&i915->gt))
^
include/linux/compiler.h:58:52: note: in definition of macro '__trace_if_var'
#define __trace_if_var(cond) (__builtin_constant_p(cond) ? (cond) : __trace_if_value(cond))
^~~~
>> drivers/gpu/drm/i915/i915_debugfs.c:3618:3: note: in expansion of macro 'if'
if (!intel_has_gpu_reset(&i915->gt))
^~
In file included from drivers/gpu/drm/i915/i915_gem_gtt.h:45:0,
from drivers/gpu/drm/i915/i915_vma.h:33,
from drivers/gpu/drm/i915/gt/uc/intel_guc.h:17,
from drivers/gpu/drm/i915/gt/uc/intel_uc.h:9,
from drivers/gpu/drm/i915/gt/intel_gt_types.h:16,
from drivers/gpu/drm/i915/i915_drv.h:80,
from drivers/gpu/drm/i915/display/intel_display_types.h:46,
from drivers/gpu/drm/i915/i915_debugfs.c:35:
drivers/gpu/drm/i915/gt/intel_reset.h:74:6: note: expected 'struct drm_i915_private *' but argument is of type 'struct intel_gt *'
bool intel_has_gpu_reset(struct drm_i915_private *i915);
^~~~~~~~~~~~~~~~~~~
In file included from include/linux/export.h:45:0,
from include/linux/linkage.h:7,
from include/linux/kernel.h:8,
from include/linux/sched/mm.h:5,
from drivers/gpu/drm/i915/i915_debugfs.c:29:
drivers/gpu/drm/i915/i915_debugfs.c:3618:28: error: passing argument 1 of 'intel_has_gpu_reset' from incompatible pointer type [-Werror=incompatible-pointer-types]
if (!intel_has_gpu_reset(&i915->gt))
^
include/linux/compiler.h:58:61: note: in definition of macro '__trace_if_var'
#define __trace_if_var(cond) (__builtin_constant_p(cond) ? (cond) : __trace_if_value(cond))
^~~~
>> drivers/gpu/drm/i915/i915_debugfs.c:3618:3: note: in expansion of macro 'if'
if (!intel_has_gpu_reset(&i915->gt))
^~
In file included from drivers/gpu/drm/i915/i915_gem_gtt.h:45:0,
from drivers/gpu/drm/i915/i915_vma.h:33,
from drivers/gpu/drm/i915/gt/uc/intel_guc.h:17,
from drivers/gpu/drm/i915/gt/uc/intel_uc.h:9,
from drivers/gpu/drm/i915/gt/intel_gt_types.h:16,
from drivers/gpu/drm/i915/i915_drv.h:80,
from drivers/gpu/drm/i915/display/intel_display_types.h:46,
from drivers/gpu/drm/i915/i915_debugfs.c:35:
drivers/gpu/drm/i915/gt/intel_reset.h:74:6: note: expected 'struct drm_i915_private *' but argument is of type 'struct intel_gt *'
bool intel_has_gpu_reset(struct drm_i915_private *i915);
^~~~~~~~~~~~~~~~~~~
In file included from include/linux/export.h:45:0,
from include/linux/linkage.h:7,
from include/linux/kernel.h:8,
from include/linux/sched/mm.h:5,
from drivers/gpu/drm/i915/i915_debugfs.c:29:
drivers/gpu/drm/i915/i915_debugfs.c:3618:28: error: passing argument 1 of 'intel_has_gpu_reset' from incompatible pointer type [-Werror=incompatible-pointer-types]
if (!intel_has_gpu_reset(&i915->gt))
^
include/linux/compiler.h:69:3: note: in definition of macro '__trace_if_value'
(cond) ? \
^~~~
include/linux/compiler.h:56:28: note: in expansion of macro '__trace_if_var'
#define if(cond, ...) if ( __trace_if_var( !!(cond , ## __VA_ARGS__) ) )
^~~~~~~~~~~~~~
>> drivers/gpu/drm/i915/i915_debugfs.c:3618:3: note: in expansion of macro 'if'
if (!intel_has_gpu_reset(&i915->gt))
^~
In file included from drivers/gpu/drm/i915/i915_gem_gtt.h:45:0,
from drivers/gpu/drm/i915/i915_vma.h:33,
from drivers/gpu/drm/i915/gt/uc/intel_guc.h:17,
from drivers/gpu/drm/i915/gt/uc/intel_uc.h:9,
from drivers/gpu/drm/i915/gt/intel_gt_types.h:16,
from drivers/gpu/drm/i915/i915_drv.h:80,
from drivers/gpu/drm/i915/display/intel_display_types.h:46,
from drivers/gpu/drm/i915/i915_debugfs.c:35:
drivers/gpu/drm/i915/gt/intel_reset.h:74:6: note: expected 'struct drm_i915_private *' but argument is of type 'struct intel_gt *'
bool intel_has_gpu_reset(struct drm_i915_private *i915);
^~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/if +3618 drivers/gpu/drm/i915/i915_debugfs.c
3601
3602 static int
3603 i915_drop_caches_set(void *data, u64 val)
3604 {
3605 struct drm_i915_private *i915 = data;
3606
3607 DRM_DEBUG("Dropping caches: 0x%08llx [0x%08llx]\n",
3608 val, val & DROP_ALL);
3609
3610 if (val & DROP_RESET_ACTIVE &&
3611 wait_for(intel_engines_are_idle(&i915->gt),
3612 I915_IDLE_ENGINES_TIMEOUT)) {
3613 /*
3614 * Only wedge if reset is supported and not disabled, otherwise
3615 * we certainly end up with the GPU terminally wedged. Inform
3616 * userspace about the problem instead.
3617 */
> 3618 if (!intel_has_gpu_reset(&i915->gt))
3619 return -EBUSY;
3620
3621 intel_gt_set_wedged(&i915->gt);
3622 }
3623
3624 /* No need to check and wait for gpu resets, only libdrm auto-restarts
3625 * on ioctls on -EAGAIN. */
3626 if (val & (DROP_ACTIVE | DROP_IDLE | DROP_RETIRE | DROP_RESET_SEQNO)) {
3627 int ret;
3628
3629 ret = mutex_lock_interruptible(&i915->drm.struct_mutex);
3630 if (ret)
3631 return ret;
3632
3633 /*
3634 * To finish the flush of the idle_worker, we must complete
3635 * the switch-to-kernel-context, which requires a double
3636 * pass through wait_for_idle: first queues the switch,
3637 * second waits for the switch.
3638 */
3639 if (ret == 0 && val & (DROP_IDLE | DROP_ACTIVE))
3640 ret = i915_gem_wait_for_idle(i915,
3641 I915_WAIT_INTERRUPTIBLE |
3642 I915_WAIT_LOCKED,
3643 MAX_SCHEDULE_TIMEOUT);
3644
3645 if (ret == 0 && val & DROP_IDLE)
3646 ret = i915_gem_wait_for_idle(i915,
3647 I915_WAIT_INTERRUPTIBLE |
3648 I915_WAIT_LOCKED,
3649 MAX_SCHEDULE_TIMEOUT);
3650
3651 if (val & DROP_RETIRE)
3652 i915_retire_requests(i915);
3653
3654 mutex_unlock(&i915->drm.struct_mutex);
3655
3656 if (ret == 0 && val & DROP_IDLE)
3657 ret = intel_gt_pm_wait_for_idle(&i915->gt);
3658 }
3659
3660 if (val & DROP_RESET_ACTIVE && intel_gt_terminally_wedged(&i915->gt))
3661 intel_gt_handle_error(&i915->gt, ALL_ENGINES, 0, NULL);
3662
3663 fs_reclaim_acquire(GFP_KERNEL);
3664 if (val & DROP_BOUND)
3665 i915_gem_shrink(i915, LONG_MAX, NULL, I915_SHRINK_BOUND);
3666
3667 if (val & DROP_UNBOUND)
3668 i915_gem_shrink(i915, LONG_MAX, NULL, I915_SHRINK_UNBOUND);
3669
3670 if (val & DROP_SHRINK_ALL)
3671 i915_gem_shrink_all(i915);
3672 fs_reclaim_release(GFP_KERNEL);
3673
3674 if (val & DROP_IDLE) {
3675 flush_delayed_work(&i915->gem.retire_work);
3676 flush_work(&i915->gem.idle_work);
3677 }
3678
3679 if (val & DROP_FREED)
3680 i915_gem_drain_freed_objects(i915);
3681
3682 return 0;
3683 }
3684
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 30179 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* ✓ Fi.CI.IGT: success for drm/i915/debugfs: Only wedge if we have reset available
2019-10-02 12:48 [RFC PATCH] drm/i915/debugfs: Only wedge if we have reset available Janusz Krzysztofik
` (3 preceding siblings ...)
2019-10-02 17:31 ` [Intel-gfx] [RFC PATCH] " kbuild test robot
@ 2019-10-03 1:07 ` Patchwork
4 siblings, 0 replies; 7+ messages in thread
From: Patchwork @ 2019-10-03 1:07 UTC (permalink / raw)
To: Janusz Krzysztofik; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/debugfs: Only wedge if we have reset available
URL : https://patchwork.freedesktop.org/series/67492/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6991_full -> Patchwork_14628_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
New tests
---------
New tests have been introduced between CI_DRM_6991_full and Patchwork_14628_full:
### New Piglit tests (7) ###
* spec@arb_gpu_shader5@texturegather@vs-rgba-0-int-cubearray:
- Statuses : 1 incomplete(s)
- Exec time: [0.0] s
* spec@arb_gpu_shader5@texturegather@vs-rgba-3-int-cube:
- Statuses : 1 incomplete(s)
- Exec time: [0.0] s
* spec@arb_gpu_shader5@texturegatheroffset@vs-rgba-3-int-2darray-const:
- Statuses : 1 incomplete(s)
- Exec time: [0.0] s
* spec@arb_gpu_shader5@texturegatheroffsets@vs-rgba-0-int-2darray:
- Statuses : 1 incomplete(s)
- Exec time: [0.0] s
* spec@arb_gpu_shader5@texturegatheroffsets@vs-rgba-1-int-2darray:
- Statuses : 1 incomplete(s)
- Exec time: [0.0] s
* spec@arb_gpu_shader5@texturegatheroffsets@vs-rgba-2-int-2darray:
- Statuses : 1 incomplete(s)
- Exec time: [0.0] s
* spec@arb_gpu_shader5@texturegatheroffsets@vs-rgba-3-int-2darray:
- Statuses : 1 incomplete(s)
- Exec time: [0.0] s
Known issues
------------
Here are the changes found in Patchwork_14628_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_shared@exec-single-timeline-bsd:
- shard-iclb: [PASS][1] -> [SKIP][2] ([fdo#110841])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb5/igt@gem_ctx_shared@exec-single-timeline-bsd.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb2/igt@gem_ctx_shared@exec-single-timeline-bsd.html
* igt@gem_exec_schedule@preempt-queue-bsd2:
- shard-iclb: [PASS][3] -> [SKIP][4] ([fdo#109276]) +7 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb2/igt@gem_exec_schedule@preempt-queue-bsd2.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb6/igt@gem_exec_schedule@preempt-queue-bsd2.html
* igt@gem_exec_schedule@preemptive-hang-bsd:
- shard-iclb: [PASS][5] -> [SKIP][6] ([fdo#111325]) +2 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb6/igt@gem_exec_schedule@preemptive-hang-bsd.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb1/igt@gem_exec_schedule@preemptive-hang-bsd.html
* igt@gem_exec_schedule@smoketest-all:
- shard-apl: [PASS][7] -> [INCOMPLETE][8] ([fdo#103927])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-apl1/igt@gem_exec_schedule@smoketest-all.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-apl6/igt@gem_exec_schedule@smoketest-all.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy-gup:
- shard-apl: [PASS][9] -> [DMESG-WARN][10] ([fdo#109385] / [fdo#111870])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-apl1/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-apl7/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
- shard-kbl: [PASS][11] -> [DMESG-WARN][12] ([fdo#111870])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-kbl7/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-kbl2/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
- shard-skl: [PASS][13] -> [DMESG-WARN][14] ([fdo#111870])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-skl10/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-skl7/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
* igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy:
- shard-snb: [PASS][15] -> [DMESG-WARN][16] ([fdo#110789] / [fdo#111870])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-snb2/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-snb5/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
* igt@gem_userptr_blits@sync-unmap:
- shard-hsw: [PASS][17] -> [DMESG-WARN][18] ([fdo#111870])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-hsw1/igt@gem_userptr_blits@sync-unmap.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-hsw6/igt@gem_userptr_blits@sync-unmap.html
* igt@gem_userptr_blits@sync-unmap-after-close:
- shard-glk: [PASS][19] -> [DMESG-WARN][20] ([fdo#111870]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-glk9/igt@gem_userptr_blits@sync-unmap-after-close.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-glk2/igt@gem_userptr_blits@sync-unmap-after-close.html
- shard-iclb: [PASS][21] -> [DMESG-WARN][22] ([fdo#111870])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb3/igt@gem_userptr_blits@sync-unmap-after-close.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb8/igt@gem_userptr_blits@sync-unmap-after-close.html
* igt@kms_big_fb@y-tiled-32bpp-rotate-0:
- shard-skl: [PASS][23] -> [DMESG-WARN][24] ([fdo#106107])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-skl8/igt@kms_big_fb@y-tiled-32bpp-rotate-0.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-skl3/igt@kms_big_fb@y-tiled-32bpp-rotate-0.html
* igt@kms_cursor_crc@pipe-c-cursor-64x64-random:
- shard-iclb: [PASS][25] -> [INCOMPLETE][26] ([fdo#107713])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb8/igt@kms_cursor_crc@pipe-c-cursor-64x64-random.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb7/igt@kms_cursor_crc@pipe-c-cursor-64x64-random.html
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-apl: [PASS][27] -> [DMESG-WARN][28] ([fdo#108566])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-apl8/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-apl8/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
* igt@kms_cursor_legacy@pipe-c-torture-move:
- shard-iclb: [PASS][29] -> [DMESG-WARN][30] ([fdo#107122])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb6/igt@kms_cursor_legacy@pipe-c-torture-move.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb7/igt@kms_cursor_legacy@pipe-c-torture-move.html
* igt@kms_flip@dpms-vs-vblank-race-interruptible:
- shard-glk: [PASS][31] -> [FAIL][32] ([fdo#111609])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-glk7/igt@kms_flip@dpms-vs-vblank-race-interruptible.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-glk5/igt@kms_flip@dpms-vs-vblank-race-interruptible.html
* igt@kms_flip@flip-vs-expired-vblank:
- shard-skl: [PASS][33] -> [FAIL][34] ([fdo#105363])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-skl9/igt@kms_flip@flip-vs-expired-vblank.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-skl3/igt@kms_flip@flip-vs-expired-vblank.html
* igt@kms_flip@flip-vs-suspend:
- shard-hsw: [PASS][35] -> [INCOMPLETE][36] ([fdo#103540])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-hsw5/igt@kms_flip@flip-vs-suspend.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-hsw2/igt@kms_flip@flip-vs-suspend.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-blt:
- shard-iclb: [PASS][37] -> [FAIL][38] ([fdo#103167])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb8/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-blt.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-blt.html
* igt@kms_plane_lowres@pipe-a-tiling-y:
- shard-iclb: [PASS][39] -> [FAIL][40] ([fdo#103166])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb5/igt@kms_plane_lowres@pipe-a-tiling-y.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb5/igt@kms_plane_lowres@pipe-a-tiling-y.html
* igt@kms_psr@psr2_primary_page_flip:
- shard-iclb: [PASS][41] -> [SKIP][42] ([fdo#109441]) +1 similar issue
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb6/igt@kms_psr@psr2_primary_page_flip.html
#### Possible fixes ####
* igt@gem_eio@suspend:
- shard-kbl: [FAIL][43] ([fdo#111550]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-kbl2/igt@gem_eio@suspend.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-kbl6/igt@gem_eio@suspend.html
* igt@gem_exec_schedule@preempt-queue-bsd:
- shard-iclb: [SKIP][45] ([fdo#111325]) -> [PASS][46] +2 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb2/igt@gem_exec_schedule@preempt-queue-bsd.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb6/igt@gem_exec_schedule@preempt-queue-bsd.html
* igt@gem_mmap_gtt@basic-small-copy-xy:
- shard-glk: [DMESG-WARN][47] ([fdo#107732]) -> [PASS][48] +1 similar issue
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-glk9/igt@gem_mmap_gtt@basic-small-copy-xy.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-glk5/igt@gem_mmap_gtt@basic-small-copy-xy.html
* igt@gem_softpin@noreloc-s3:
- shard-apl: [DMESG-WARN][49] ([fdo#108566]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-apl2/igt@gem_softpin@noreloc-s3.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-apl2/igt@gem_softpin@noreloc-s3.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy:
- shard-glk: [DMESG-WARN][51] ([fdo#111870]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-glk3/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-glk6/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
- shard-skl: [DMESG-WARN][53] ([fdo#111870]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-skl6/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-skl2/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
- shard-apl: [DMESG-WARN][55] ([fdo#109385] / [fdo#111870]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-apl6/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-apl4/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
* igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy:
- shard-iclb: [DMESG-WARN][57] ([fdo#111870]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb4/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb4/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
- shard-hsw: [DMESG-WARN][59] ([fdo#111870]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-hsw5/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-hsw7/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
* {igt@i915_pm_dc@dc6-dpms}:
- shard-iclb: [FAIL][61] ([fdo#110548]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb3/igt@i915_pm_dc@dc6-dpms.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb2/igt@i915_pm_dc@dc6-dpms.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- shard-kbl: [FAIL][63] ([fdo#105363]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-kbl1/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-kbl7/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
- shard-skl: [FAIL][65] ([fdo#105363]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-skl1/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-skl10/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-skl: [INCOMPLETE][67] ([fdo#109507]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-skl8/igt@kms_flip@flip-vs-suspend-interruptible.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-skl5/igt@kms_flip@flip-vs-suspend-interruptible.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-render:
- shard-iclb: [FAIL][69] ([fdo#103167]) -> [PASS][70] +5 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb7/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-render.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb3/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-render.html
* igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min:
- shard-skl: [FAIL][71] ([fdo#108145]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-skl6/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-skl6/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [FAIL][73] ([fdo#108145] / [fdo#110403]) -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-skl8/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-skl9/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html
* igt@kms_psr@psr2_dpms:
- shard-iclb: [SKIP][75] ([fdo#109441]) -> [PASS][76] +1 similar issue
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb5/igt@kms_psr@psr2_dpms.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb2/igt@kms_psr@psr2_dpms.html
* igt@kms_setmode@basic:
- shard-apl: [FAIL][77] ([fdo#99912]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-apl1/igt@kms_setmode@basic.html
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-apl4/igt@kms_setmode@basic.html
* igt@perf_pmu@cpu-hotplug:
- shard-glk: [DMESG-WARN][79] ([fdo#107732] / [fdo#111800]) -> [PASS][80]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-glk9/igt@perf_pmu@cpu-hotplug.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-glk5/igt@perf_pmu@cpu-hotplug.html
* igt@prime_busy@after-bsd2:
- shard-iclb: [SKIP][81] ([fdo#109276]) -> [PASS][82] +9 similar issues
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb5/igt@prime_busy@after-bsd2.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb2/igt@prime_busy@after-bsd2.html
* igt@prime_busy@wait-before-bsd:
- shard-iclb: [WARN][83] -> [PASS][84]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb1/igt@prime_busy@wait-before-bsd.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb4/igt@prime_busy@wait-before-bsd.html
#### Warnings ####
* igt@gem_mocs_settings@mocs-reset-bsd2:
- shard-iclb: [FAIL][85] ([fdo#111330]) -> [SKIP][86] ([fdo#109276])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-iclb4/igt@gem_mocs_settings@mocs-reset-bsd2.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-iclb5/igt@gem_mocs_settings@mocs-reset-bsd2.html
* igt@gem_userptr_blits@coherency-sync:
- shard-snb: [DMESG-WARN][87] ([fdo#111870]) -> [DMESG-WARN][88] ([fdo#110789] / [fdo#111870])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6991/shard-snb1/igt@gem_userptr_blits@coherency-sync.html
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/shard-snb6/igt@gem_userptr_blits@coherency-sync.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103540]: https://bugs.freedesktop.org/show_bug.cgi?id=103540
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363
[fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107
[fdo#107122]: https://bugs.freedesktop.org/show_bug.cgi?id=107122
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107732]: https://bugs.freedesktop.org/show_bug.cgi?id=107732
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109385]: https://bugs.freedesktop.org/show_bug.cgi?id=109385
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109507]: https://bugs.freedesktop.org/show_bug.cgi?id=109507
[fdo#110403]: https://bugs.freedesktop.org/show_bug.cgi?id=110403
[fdo#110548]: https://bugs.freedesktop.org/show_bug.cgi?id=110548
[fdo#110789]: https://bugs.freedesktop.org/show_bug.cgi?id=110789
[fdo#110841]: https://bugs.freedesktop.org/show_bug.cgi?id=110841
[fdo#111325]: https://bugs.freedesktop.org/show_bug.cgi?id=111325
[fdo#111330]: https://bugs.freedesktop.org/show_bug.cgi?id=111330
[fdo#111550]: https://bugs.freedesktop.org/show_bug.cgi?id=111550
[fdo#111609]: https://bugs.freedesktop.org/show_bug.cgi?id=111609
[fdo#111800]: https://bugs.freedesktop.org/show_bug.cgi?id=111800
[fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
[fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912
Participating hosts (11 -> 10)
------------------------------
Missing (1): shard-tglb
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_6991 -> Patchwork_14628
CI-20190529: 20190529
CI_DRM_6991: 1f02b477cc08d4560a0c2cf6cc98340e09c7c734 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5209: ec639c89860b859fdf4b038c2fa8ad593bd6909e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_14628: 4445d40108bea3af6359252de635ce25010c132d @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14628/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2019-10-03 1:07 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-02 12:48 [RFC PATCH] drm/i915/debugfs: Only wedge if we have reset available Janusz Krzysztofik
2019-10-02 15:45 ` Tvrtko Ursulin
2019-10-02 15:59 ` Chris Wilson
2019-10-02 16:33 ` [Intel-gfx] " kbuild test robot
2019-10-02 17:00 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-10-02 17:31 ` [Intel-gfx] [RFC PATCH] " kbuild test robot
2019-10-03 1:07 ` ✓ Fi.CI.IGT: success for " Patchwork
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.