From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for series starting with drm/i915: Revoke mmaps and prevent access to fence registers across reset (rev4)
Date: Thu, 31 Jan 2019 13:45:54 -0000 [thread overview]
Message-ID: <20190131134554.28477.9181@emeril.freedesktop.org> (raw)
In-Reply-To: <20190131120105.23144-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with drm/i915: Revoke mmaps and prevent access to fence registers across reset (rev4)
URL : https://patchwork.freedesktop.org/series/56042/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5518 -> Patchwork_12109
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/56042/revisions/4/mbox/
Known issues
------------
Here are the changes found in Patchwork_12109 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_suspend@basic-s4-devices:
- fi-blb-e6850: PASS -> INCOMPLETE [fdo#107718]
#### Possible fixes ####
* igt@i915_selftest@live_hangcheck:
- fi-skl-iommu: INCOMPLETE [fdo#108602] / [fdo#108744] -> PASS
* igt@kms_busy@basic-flip-a:
- fi-kbl-7567u: {SKIP} [fdo#109271] / [fdo#109278] -> PASS +2
* igt@kms_pipe_crc_basic@read-crc-pipe-b-frame-sequence:
- fi-byt-clapper: FAIL [fdo#103191] / [fdo#107362] -> PASS
* igt@pm_rpm@module-reload:
- fi-skl-6770hq: FAIL [fdo#108511] -> PASS
* igt@prime_vgem@basic-fence-flip:
- fi-gdg-551: DMESG-FAIL [fdo#103182] -> PASS
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103182]: https://bugs.freedesktop.org/show_bug.cgi?id=103182
[fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
[fdo#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
[fdo#108511]: https://bugs.freedesktop.org/show_bug.cgi?id=108511
[fdo#108602]: https://bugs.freedesktop.org/show_bug.cgi?id=108602
[fdo#108744]: https://bugs.freedesktop.org/show_bug.cgi?id=108744
[fdo#108915]: https://bugs.freedesktop.org/show_bug.cgi?id=108915
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109516]: https://bugs.freedesktop.org/show_bug.cgi?id=109516
Participating hosts (43 -> 46)
------------------------------
Additional (6): fi-bxt-dsi fi-ivb-3770 fi-icl-y fi-bsw-kefka fi-skl-6600u fi-snb-2600
Missing (3): fi-ilk-m540 fi-byt-squawks fi-bsw-cyan
Build changes
-------------
* Linux: CI_DRM_5518 -> Patchwork_12109
CI_DRM_5518: 2369fd28d3a46b865f6d4f1d309a4c6b7b4e6d93 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4801: 6f6bacf12759fb319ade3ba37861ae711f8a5cd9 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_12109: b14cb740ba0da05e4c0bc3d7c4384487aa938dd8 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
b14cb740ba0d drm/i915: Serialise resets with wedging
4e2a0fb09b7a drm/i915: Wait for old resets before applying debugfs/i915_wedged
6c7dbf50ca32 drm/i915: Uninterruptibly drain the timelines on unwedging
2b82a38d5c70 drm/i915: Force the GPU reset upon wedging
2d631da15f0d drm/i915: Revoke mmaps and prevent access to fence registers across reset
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12109/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-01-31 13:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 12:01 [PATCH 1/5] drm/i915: Revoke mmaps and prevent access to fence registers across reset Chris Wilson
2019-01-31 12:01 ` [PATCH 2/5] drm/i915: Force the GPU reset upon wedging Chris Wilson
2019-01-31 12:01 ` [PATCH 3/5] drm/i915: Uninterruptibly drain the timelines on unwedging Chris Wilson
2019-01-31 12:01 ` [PATCH 4/5] drm/i915: Wait for old resets before applying debugfs/i915_wedged Chris Wilson
2019-01-31 12:01 ` [PATCH 5/5] drm/i915: Serialise resets with wedging Chris Wilson
2019-01-31 12:13 ` [PATCH] " Chris Wilson
2019-01-31 12:14 ` Chris Wilson
2019-01-31 12:17 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/5] drm/i915: Revoke mmaps and prevent access to fence registers across reset Patchwork
2019-01-31 12:39 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-01-31 12:40 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/5] drm/i915: Revoke mmaps and prevent access to fence registers across reset (rev3) Patchwork
2019-01-31 12:59 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-01-31 13:12 ` [PATCH] drm/i915: Revoke mmaps and prevent access to fence registers across reset Chris Wilson
2019-01-31 13:23 ` ✗ Fi.CI.SPARSE: warning for series starting with drm/i915: Revoke mmaps and prevent access to fence registers across reset (rev4) Patchwork
2019-01-31 13:45 ` Patchwork [this message]
2019-01-31 22:33 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-01-31 22:37 ` Chris Wilson
2019-02-01 21:25 ` [PATCH 1/5] drm/i915: Revoke mmaps and prevent access to fence registers across reset kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190131134554.28477.9181@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox