From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Use enum plane_id for frontbuffer tracking
Date: Wed, 24 Jan 2018 19:09:28 +0200 [thread overview]
Message-ID: <20180124170928.GU5453@intel.com> (raw)
In-Reply-To: <20180124040449.27058.2381@emeril.freedesktop.org>
On Wed, Jan 24, 2018 at 04:04:49AM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Use enum plane_id for frontbuffer tracking
> URL : https://patchwork.freedesktop.org/series/36991/
> State : failure
>
> == Summary ==
>
> Test kms_flip:
> Subgroup 2x-wf_vblank-ts-check-interruptible:
> pass -> FAIL (shard-hsw)
missed a vblank
(kms_flip:8780) CRITICAL: Test assertion failure function calibrate_ts,
file kms_flip.c:1199:
(kms_flip:8780) CRITICAL: Failed assertion: ev.sequence == last_seq + 1
(kms_flip:8780) CRITICAL: Last errno: 4, Interrupted system call
(kms_flip:8780) CRITICAL: error: 56602 != 56601
> Subgroup flip-vs-expired-vblank-interruptible:
> fail -> PASS (shard-hsw) fdo#102887
> Subgroup vblank-vs-modeset-suspend:
> pass -> SKIP (shard-snb) fdo#102365 +1
> Subgroup vblank-vs-modeset-suspend-interruptible:
> pass -> DMESG-WARN (shard-snb)
[ 116.297966] unchecked MSR access error: RDMSR from 0x1b0 at rIP:
0xffffffff8102e256 (init_intel_energy_perf.part.3+0x6/0xa0)
https://bugs.freedesktop.org/show_bug.cgi?id=102365
> Subgroup plain-flip-fb-recreate-interruptible:
> pass -> FAIL (shard-hsw) fdo#100368
> Test kms_sysfs_edid_timing:
> warn -> PASS (shard-apl) fdo#100047
> Test gem_softpin:
> Subgroup noreloc-s4:
> fail -> SKIP (shard-snb) fdo#103375
> Test perf:
> Subgroup buffer-fill:
> pass -> FAIL (shard-apl) fdo#103755
>
> fdo#102887 https://bugs.freedesktop.org/show_bug.cgi?id=102887
> fdo#102365 https://bugs.freedesktop.org/show_bug.cgi?id=102365
> fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
> fdo#100047 https://bugs.freedesktop.org/show_bug.cgi?id=100047
> fdo#103375 https://bugs.freedesktop.org/show_bug.cgi?id=103375
> fdo#103755 https://bugs.freedesktop.org/show_bug.cgi?id=103755
>
> shard-apl total:2753 pass:1716 dwarn:1 dfail:0 fail:23 skip:1013 time:14064s
> shard-hsw total:2753 pass:1723 dwarn:1 dfail:0 fail:13 skip:1015 time:15328s
> shard-snb total:2753 pass:1317 dwarn:2 dfail:0 fail:9 skip:1425 time:7847s
> Blacklisted hosts:
> shard-kbl total:2753 pass:1821 dwarn:16 dfail:1 fail:24 skip:891 time:11113s
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7755/shards.html
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-01-24 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 18:33 [PATCH] drm/i915: Use enum plane_id for frontbuffer tracking Ville Syrjala
2018-01-23 19:00 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-01-23 21:11 ` [PATCH] " Chris Wilson
2018-01-24 17:36 ` Ville Syrjälä
2018-01-24 18:19 ` Ville Syrjälä
2018-01-23 21:12 ` Chris Wilson
2018-01-24 4:04 ` ✗ Fi.CI.IGT: failure for " Patchwork
2018-01-24 17:09 ` Ville Syrjälä [this message]
2018-01-24 4:16 ` [PATCH] " Pandiyan, Dhinakaran
2018-01-24 15:16 ` Ville Syrjälä
2018-01-24 19:03 ` Pandiyan, Dhinakaran
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=20180124170928.GU5453@intel.com \
--to=ville.syrjala@linux.intel.com \
--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