From: Bob Paauwe <bob.j.paauwe@intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Read DPCD when connector forced on.
Date: Fri, 1 Apr 2016 10:53:09 -0700 [thread overview]
Message-ID: <20160401105309.79aea711@bpaauwe-desk.fm.intel.com> (raw)
In-Reply-To: <20160401170337.30950.28765@emeril.freedesktop.org>
On Fri, 1 Apr 2016 17:03:37 +0000
Patchwork <patchwork@emeril.freedesktop.org> wrote:
> == Series Details ==
>
> Series: drm/i915: Read DPCD when connector forced on.
> URL : https://patchwork.freedesktop.org/series/5185/
> State : failure
>
> == Summary ==
>
> Series 5185v1 drm/i915: Read DPCD when connector forced on.
> http://patchwork.freedesktop.org/api/1.0/series/5185/revisions/1/mbox/
>
> Test kms_flip:
> Subgroup basic-flip-vs-modeset:
> pass -> DMESG-WARN (ilk-hp8440p) UNSTABLE
Unrelated: CPU pipe A FIFO underrun and test is not using DP ports.
> Subgroup basic-flip-vs-wf_vblank:
> pass -> FAIL (snb-x220t)
Failure is on vga connector so unrelated to code change in DP code.
> Test kms_force_connector_basic:
> Subgroup force-edid:
> skip -> PASS (ivb-t430s)
>
> bdw-nuci7 total:196 pass:184 dwarn:0 dfail:0 fail:0 skip:12
> bdw-ultra total:196 pass:175 dwarn:0 dfail:0 fail:0 skip:21
> bsw-nuc-2 total:196 pass:159 dwarn:0 dfail:0 fail:0 skip:37
> byt-nuc total:196 pass:161 dwarn:0 dfail:0 fail:0 skip:35
> hsw-brixbox total:196 pass:174 dwarn:0 dfail:0 fail:0 skip:22
> hsw-gt2 total:196 pass:179 dwarn:0 dfail:0 fail:0 skip:17
> ilk-hp8440p total:196 pass:131 dwarn:1 dfail:0 fail:0 skip:64
> ivb-t430s total:196 pass:171 dwarn:0 dfail:0 fail:0 skip:25
> skl-i7k-2 total:196 pass:173 dwarn:0 dfail:0 fail:0 skip:23
> skl-nuci5 total:196 pass:185 dwarn:0 dfail:0 fail:0 skip:11
> snb-dellxps total:196 pass:162 dwarn:0 dfail:0 fail:0 skip:34
> snb-x220t total:196 pass:161 dwarn:0 dfail:0 fail:2 skip:33
>
> Results at /archive/results/CI_IGT_test/Patchwork_1778/
>
> 38b47023a604068e2a222ac166f5f8ef7d56e352 drm-intel-nightly: 2016y-04m-01d-12h-04m-08s UTC integration manifest
> a73fbb388ca70b2ca76c82124fde009c47cc33cd drm/i915: Read DPCD when connector forced on.
>
--
--
Bob Paauwe
Bob.J.Paauwe@intel.com
IOTG / PED Software Organization
Intel Corp. Folsom, CA
(916) 356-6193
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-04-01 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 16:20 [PATCH] drm/i915: Read DPCD when connector forced on Bob Paauwe
2016-04-01 17:03 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-04-01 17:53 ` Bob Paauwe [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=20160401105309.79aea711@bpaauwe-desk.fm.intel.com \
--to=bob.j.paauwe@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.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.