From: Ander Conselvan De Oliveira <conselvan2@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Wait for vblank in i9xx_disable_crtc() for gen 2 only
Date: Thu, 18 Feb 2016 11:15:32 +0200 [thread overview]
Message-ID: <1455786932.4065.5.camel@gmail.com> (raw)
In-Reply-To: <20160217082701.18090.16813@annarchy.freedesktop.org>
On Wed, 2016-02-17 at 08:27 +0000, Patchwork wrote:
> == Summary ==
>
> Series 3496v1 drm/i915: Wait for vblank in i9xx_disable_crtc() for gen 2 only
> http://patchwork.freedesktop.org/api/1.0/series/3496/revisions/1/mbox/
>
> Test gem_ringfill:
> Subgroup basic-default-hang:
> incomplete -> PASS (snb-dellxps)
> Test kms_flip:
> Subgroup basic-flip-vs-modeset:
> pass -> DMESG-WARN (ilk-hp8440p) UNSTABLE
https://bugs.freedesktop.org/show_bug.cgi?id=93787
> Test kms_pipe_crc_basic:
> Subgroup suspend-read-crc-pipe-a:
> dmesg-warn -> PASS (skl-i5k-2)
> Subgroup suspend-read-crc-pipe-b:
> pass -> INCOMPLETE (hsw-gt2)
I'm pretty sure this is a fluke. The code the patch changes doesn't even run on
HSW.
What is the normal procedure for this kind of issues?
> Subgroup suspend-read-crc-pipe-c:
> pass -> DMESG-WARN (skl-i5k-2)
https://bugs.freedesktop.org/show_bug.cgi?id=93294
> dmesg-warn -> PASS (bsw-nuc-2)
> Test pm_rpm:
> Subgroup basic-pci-d3-state:
> fail -> PASS (bdw-nuci7)
> Subgroup basic-rte:
> dmesg-warn -> PASS (bsw-nuc-2)
>
> bdw-nuci7 total:162 pass:152 dwarn:0 dfail:0 fail:0 skip:10
> bdw-ultra total:165 pass:152 dwarn:0 dfail:0 fail:0 skip:13
> bsw-nuc-2 total:165 pass:136 dwarn:0 dfail:0 fail:0 skip:29
> byt-nuc total:165 pass:140 dwarn:1 dfail:0 fail:0 skip:24
> hsw-brixbox total:165 pass:151 dwarn:0 dfail:0 fail:0 skip:14
> hsw-gt2 total:127 pass:118 dwarn:0 dfail:0 fail:0 skip:8
> ilk-hp8440p total:165 pass:115 dwarn:1 dfail:0 fail:1 skip:48
> skl-i5k-2 total:165 pass:149 dwarn:1 dfail:0 fail:0 skip:15
> snb-dellxps total:165 pass:142 dwarn:0 dfail:0 fail:1 skip:22
>
> Results at /archive/results/CI_IGT_test/Patchwork_1418/
>
> bd0b1a9aa8b7fdb2e06a5cbf1756ef93de2fa3fd drm-intel-nightly: 2016y-02m-16d-17h
> -53m-05s UTC integration manifest
> 3623c71eeb82092a0774b8b959a6a367ffca46c2 drm/i915: Wait for vblank in
> i9xx_disable_crtc() for gen 2 only
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-02-18 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 17:53 [PATCH] drm/i915: Wait for vblank in i9xx_disable_crtc() for gen 2 only Ander Conselvan de Oliveira
2016-02-17 8:27 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-02-18 9:15 ` Ander Conselvan De Oliveira [this message]
2016-02-17 9:25 ` [PATCH] " Jani Nikula
2016-02-17 12:39 ` Ander Conselvan De Oliveira
2016-02-17 16:21 ` Daniel Vetter
2016-02-17 17:16 ` Jani Nikula
2016-02-17 17:56 ` Daniel Vetter
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=1455786932.4065.5.camel@gmail.com \
--to=conselvan2@gmail.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;
as well as URLs for NNTP newsgroup(s).