From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for series starting with [1/7] drm/i915: Flush submission tasklet after bumping priority (rev2)
Date: Mon, 07 May 2018 10:14:07 -0000 [thread overview]
Message-ID: <20180507101407.28244.8504@emeril.freedesktop.org> (raw)
In-Reply-To: <20180507092527.7359-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/7] drm/i915: Flush submission tasklet after bumping priority (rev2)
URL : https://patchwork.freedesktop.org/series/42800/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_4150 -> Patchwork_8924 =
== Summary - FAILURE ==
Serious unknown changes coming with Patchwork_8924 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_8924, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://patchwork.freedesktop.org/api/1.0/series/42800/revisions/2/mbox/
== Possible new issues ==
Here are the unknown changes that may have been introduced in Patchwork_8924:
=== IGT changes ===
==== Possible regressions ====
igt@gem_exec_gttfill@basic:
fi-skl-guc: PASS -> INCOMPLETE
== Known issues ==
Here are the changes found in Patchwork_8924 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@gem_ringfill@basic-default-hang:
fi-pnv-d510: NOTRUN -> DMESG-WARN (fdo#101600)
igt@kms_chamelium@hdmi-hpd-fast:
fi-kbl-7500u: SKIP -> FAIL (fdo#102672, fdo#103841)
==== Possible fixes ====
igt@kms_frontbuffer_tracking@basic:
fi-hsw-4200u: DMESG-FAIL (fdo#102614, fdo#106103) -> PASS
igt@kms_pipe_crc_basic@read-crc-pipe-b:
fi-skl-6700k2: FAIL (fdo#103191, fdo#104724) -> PASS
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
fi-glk-j4005: DMESG-WARN (fdo#106097) -> PASS
fdo#101600 https://bugs.freedesktop.org/show_bug.cgi?id=101600
fdo#102614 https://bugs.freedesktop.org/show_bug.cgi?id=102614
fdo#102672 https://bugs.freedesktop.org/show_bug.cgi?id=102672
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#103841 https://bugs.freedesktop.org/show_bug.cgi?id=103841
fdo#104724 https://bugs.freedesktop.org/show_bug.cgi?id=104724
fdo#106097 https://bugs.freedesktop.org/show_bug.cgi?id=106097
fdo#106103 https://bugs.freedesktop.org/show_bug.cgi?id=106103
== Participating hosts (38 -> 37) ==
Additional (2): fi-kbl-7560u fi-pnv-d510
Missing (3): fi-ctg-p8600 fi-ilk-m540 fi-skl-6700hq
== Build changes ==
* Linux: CI_DRM_4150 -> Patchwork_8924
CI_DRM_4150: 93d32416ba4b1dae9451fec28aaa71915d770f51 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4463: 91b5a3ef5516b29584ea4567b0f5ffa18219b29f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_8924: a6ecf3114c11797b6f46d2e9fb7172d69a676305 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4463: 33e58d5583eb7ed3966a1b905f875a1dfa959f6b @ git://anongit.freedesktop.org/piglit
== Linux commits ==
a6ecf3114c11 drm/i915: Speed up idle detection by kicking the tasklets
637900fb273c drm/i915/execlists: Direct submission from irq handler
dbee74d26584 drm/i915/execlists: Direct submit onto idle engines
26afd02dbd15 drm/i915/guc: Make submission tasklet hardirq safe
9a183196dc0c drm/i915/execlists: Make submission tasklet hardirq safe
3fff19362e88 drm/i915: Combine set-wedged protection and tasklet kicking
a337a1138169 drm/i915: Flush submission tasklet after bumping priority
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_8924/issues.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-05-07 10:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 9:25 [PATCH 1/7] drm/i915: Flush submission tasklet after bumping priority Chris Wilson
2018-05-07 9:25 ` [PATCH 2/7] drm/i915: Combine set-wedged protection and tasklet kicking Chris Wilson
2018-05-07 12:09 ` Mika Kuoppala
2018-05-07 12:16 ` Chris Wilson
2018-05-07 9:25 ` [PATCH 3/7] drm/i915/execlists: Make submission tasklet hardirq safe Chris Wilson
2018-05-07 9:25 ` [PATCH 4/7] drm/i915/guc: " Chris Wilson
2018-05-07 9:25 ` [PATCH 5/7] drm/i915/execlists: Direct submit onto idle engines Chris Wilson
2018-05-07 9:25 ` [PATCH 6/7] drm/i915/execlists: Direct submission from irq handler Chris Wilson
2018-05-07 9:25 ` [PATCH 7/7] drm/i915: Speed up idle detection by kicking the tasklets Chris Wilson
2018-05-07 9:35 ` [PATCH v3] " Chris Wilson
2018-05-07 14:08 ` kbuild test robot
2018-05-07 9:33 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/7] drm/i915: Flush submission tasklet after bumping priority Patchwork
2018-05-07 9:35 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-05-07 9:52 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-05-07 9:57 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/7] drm/i915: Flush submission tasklet after bumping priority (rev2) Patchwork
2018-05-07 9:59 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-05-07 10:14 ` Patchwork [this message]
2018-05-07 11:15 ` [PATCH 1/7] drm/i915: Flush submission tasklet after bumping priority Mika Kuoppala
2018-05-07 11:19 ` Chris Wilson
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=20180507101407.28244.8504@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 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.