From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Ro.CI.BAT: failure for drm/i915: Store number of active engines in device info
Date: Thu, 11 Aug 2016 11:34:55 +0100 [thread overview]
Message-ID: <57AC54CF.7080009@linux.intel.com> (raw)
In-Reply-To: <20160810172750.24583.31941@emeril.freedesktop.org>
On 10/08/16 18:27, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Store number of active engines in device info
> URL : https://patchwork.freedesktop.org/series/10921/
> State : failure
>
> == Summary ==
>
> Series 10921v1 drm/i915: Store number of active engines in device info
> http://patchwork.freedesktop.org/api/1.0/series/10921/revisions/1/mbox
>
> Test kms_cursor_legacy:
> Subgroup basic-cursor-vs-flip-varying-size:
> fail -> PASS (ro-ilk1-i5-650)
> Subgroup basic-flip-vs-cursor-legacy:
> fail -> PASS (ro-skl3-i5-6260u)
> fail -> PASS (ro-bdw-i7-5557U)
> Subgroup basic-flip-vs-cursor-varying-size:
> fail -> PASS (ro-bdw-i5-5250u)
> Test kms_pipe_crc_basic:
> Subgroup nonblocking-crc-pipe-b-frame-sequence:
> pass -> FAIL (ro-bdw-i7-5600u)
(kms_pipe_crc_basic:8255) CRITICAL: Failed assertion: crcs[j].frame + 1
== crcs[j + 1].frame
Some modesetting problem, no idea, raised a new bug:
https://bugs.freedesktop.org/show_bug.cgi?id=97294
> Subgroup suspend-read-crc-pipe-b:
> dmesg-warn -> SKIP (ro-bdw-i7-5557U)
> Subgroup suspend-read-crc-pipe-c:
> skip -> DMESG-WARN (ro-bdw-i5-5250u)
https://bugs.freedesktop.org/show_bug.cgi?id=96614
[ 482.345981] [drm:intel_dp_link_training_clock_recovery [i915]]
*ERROR* failed to enable link training
[ 482.431185] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to
start channel equalization
>
> ro-bdw-i5-5250u total:240 pass:219 dwarn:2 dfail:0 fail:1 skip:18
> ro-bdw-i7-5557U total:240 pass:220 dwarn:1 dfail:0 fail:0 skip:19
> ro-bdw-i7-5600u total:240 pass:206 dwarn:0 dfail:0 fail:2 skip:32
> ro-bsw-n3050 total:240 pass:194 dwarn:0 dfail:0 fail:4 skip:42
> ro-byt-n2820 total:240 pass:197 dwarn:0 dfail:0 fail:3 skip:40
> ro-hsw-i3-4010u total:240 pass:214 dwarn:0 dfail:0 fail:0 skip:26
> ro-hsw-i7-4770r total:240 pass:214 dwarn:0 dfail:0 fail:0 skip:26
> ro-ilk1-i5-650 total:235 pass:174 dwarn:0 dfail:0 fail:1 skip:60
> ro-ivb-i7-3770 total:240 pass:205 dwarn:0 dfail:0 fail:0 skip:35
> ro-ivb2-i7-3770 total:240 pass:209 dwarn:0 dfail:0 fail:0 skip:31
> ro-skl3-i5-6260u total:240 pass:223 dwarn:0 dfail:0 fail:3 skip:14
>
> Results at /archive/results/CI_IGT_test/RO_Patchwork_1825/
>
> 3aec82c drm-intel-nightly: 2016y-08m-10d-15h-08m-03s UTC integration manifest
> 11c946d drm/i915: Store number of active engines in device info
Merged to dinq, thanks for the review!
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-08-11 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 15:22 [PATCH] drm/i915: Store number of active engines in device info Tvrtko Ursulin
2016-08-10 15:41 ` Dave Gordon
2016-08-10 15:46 ` Chris Wilson
2016-08-10 17:27 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-08-11 10:34 ` Tvrtko Ursulin [this message]
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=57AC54CF.7080009@linux.intel.com \
--to=tvrtko.ursulin@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