From: Dave Gordon <david.s.gordon@intel.com>
To: intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Subject: Re: ✗ Ro.CI.BAT: warning for drm/i915/guc: Protect against HAS_GUC_* returning true values other than one (rev4)
Date: Thu, 14 Jul 2016 14:33:51 +0100 [thread overview]
Message-ID: <578794BF.7040304@intel.com> (raw)
In-Reply-To: <20160713133822.7934.96053@emeril.freedesktop.org>
On 13/07/16 14:38, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/guc: Protect against HAS_GUC_* returning true values other than one (rev4)
> URL : https://patchwork.freedesktop.org/series/9473/
> State : warning
>
> == Summary ==
>
> Series 9473v4 drm/i915/guc: Protect against HAS_GUC_* returning true values other than one
> http://patchwork.freedesktop.org/api/1.0/series/9473/revisions/4/mbox
>
> Test gem_exec_suspend:
> Subgroup basic-s3:
> pass -> DMESG-WARN (ro-bdw-i7-5557U)
> Test kms_pipe_crc_basic:
> Subgroup suspend-read-crc-pipe-a:
> dmesg-warn -> PASS (ro-skl3-i5-6260u)
> skip -> DMESG-WARN (ro-bdw-i7-5557U)
Both of these look like
https://bugs.freedesktop.org/show_bug.cgi?id=96614
[BAT BDW] *ERROR* failed to enable link training/failed to start channel
equalization
.Dave.
> fi-kbl-qkkr total:237 pass:174 dwarn:27 dfail:2 fail:7 skip:27
> fi-skl-i5-6260u total:237 pass:189 dwarn:27 dfail:2 fail:7 skip:12
> fi-skl-i7-6700k total:237 pass:200 dwarn:2 dfail:0 fail:9 skip:26
> ro-bdw-i5-5250u total:237 pass:210 dwarn:2 dfail:0 fail:9 skip:16
> ro-bdw-i7-5557U total:237 pass:210 dwarn:3 dfail:0 fail:9 skip:15
> ro-bsw-n3050 total:217 pass:170 dwarn:0 dfail:0 fail:4 skip:42
> ro-skl3-i5-6260u total:237 pass:213 dwarn:3 dfail:0 fail:9 skip:12
> fi-snb-i7-2600 failed to connect after reboot
> ro-bdw-i7-5600u failed to connect after reboot
> ro-byt-n2820 failed to connect after reboot
> ro-hsw-i3-4010u failed to connect after reboot
> ro-hsw-i7-4770r failed to connect after reboot
> ro-ilk1-i5-650 failed to connect after reboot
> ro-ilk-i7-620lm failed to connect after reboot
> ro-ivb-i7-3770 failed to connect after reboot
> ro-snb-i7-2620M failed to connect after reboot
>
> Results at /archive/results/CI_IGT_test/RO_Patchwork_1483/
>
> e8b1f0b drm-intel-nightly: 2016y-07m-13d-10h-57m-19s UTC integration manifest
> 40c374e drm/i915/guc: symbolic names for user load/submission preferences
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-07-14 13:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 14:30 [PATCH] drm/i915/guc: Protect against HAS_GUC_* returning true values other than one Tvrtko Ursulin
2016-07-04 14:54 ` Chris Wilson
2016-07-04 15:03 ` ✗ Ro.CI.BAT: warning for " Patchwork
2016-07-05 10:58 ` [PATCH] " Antoine, Peter
2016-07-05 11:50 ` Dave Gordon
2016-07-05 11:56 ` Tvrtko Ursulin
2016-07-05 12:32 ` Dave Gordon
2016-07-13 13:01 ` [PATCH] drm/i915/guc: symbolic names for user load/submission preferences Dave Gordon
2016-07-05 12:54 ` ✗ Ro.CI.BAT: failure for drm/i915/guc: Protect against HAS_GUC_* returning true values other than one (rev3) Patchwork
2016-07-13 13:38 ` ✗ Ro.CI.BAT: warning for drm/i915/guc: Protect against HAS_GUC_* returning true values other than one (rev4) Patchwork
2016-07-14 13:33 ` Dave Gordon [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=578794BF.7040304@intel.com \
--to=david.s.gordon@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.intel.com \
/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