From: Imre Deak <imre.deak@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/kbl: Don't WARN for expected secondary MISC IO power well request
Date: Tue, 19 Apr 2016 15:38:55 +0300 [thread overview]
Message-ID: <1461069535.10192.17.camel@intel.com> (raw)
In-Reply-To: <20160419105615.20310.16534@emeril.freedesktop.org>
On ti, 2016-04-19 at 10:56 +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/kbl: Don't WARN for expected secondary MISC IO power
> well request
> URL : https://patchwork.freedesktop.org/series/5917/
> State : failure
>
> == Summary ==
>
> Series 5917v1 drm/i915/kbl: Don't WARN for expected secondary MISC IO
> power well request
> http://patchwork.freedesktop.org/api/1.0/series/5917/revisions/1/mbox
> /
>
> Test kms_flip:
> Subgroup basic-flip-vs-modeset:
> pass -> DMESG-WARN (skl-i7k-2)
Pre-existing issue: set CRTC IOCTL->intel_atomic_commit() followed by
vlank wait timeout and "Removing stuck page" WARN:
https://bugs.freedesktop.org/show_bug.cgi?id=94572
> Subgroup basic-flip-vs-wf_vblank:
> pass -> FAIL (hsw-brixbox)
Pre-existing:
(kms_flip:6669) CRITICAL: Test assertion failure function check_state, file kms_flip.c:692:
(kms_flip:6669) CRITICAL: Failed assertion: fabs((((double) diff.tv_usec) - usec_interflip) / usec_interflip) <= 0.005
(kms_flip:6669) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_flip:6669) CRITICAL: inter-vblank ts jitter: 0s, 183345usec
> pass -> FAIL (byt-nuc)
Pre-existing:
(kms_flip:7293) CRITICAL: Test assertion failure function check_state, file kms_flip.c:692:
(kms_flip:7293) CRITICAL: Failed assertion: fabs((((double) diff.tv_usec) - usec_interflip) / usec_interflip) <= 0.005
(kms_flip:7293) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_flip:7293) CRITICAL: inter-vblank ts jitter: 0s, 183237usec
Subtest basic-flip-vs-wf_vblank failed.
> Test kms_pipe_crc_basic:
> Subgroup read-crc-pipe-a-frame-sequence:
> fail -> PASS (ivb-t430s)
>
> bdw-
> nuci7 total:192 pass:180 dwarn:0 dfail:0 fail:0 skip:1
> 2
> bdw-
> ultra total:127 pass:105 dwarn:0 dfail:0 fail:0 skip:2
> 2
> byt-
> nuc total:191 pass:152 dwarn:0 dfail:0 fail:1 skip:3
> 8
> hsw-
> brixbox total:192 pass:167 dwarn:0 dfail:0 fail:1 skip:2
> 4
> hsw-
> gt2 total:192 pass:173 dwarn:0 dfail:0 fail:0 skip:1
> 9
> ivb-
> t430s total:192 pass:164 dwarn:0 dfail:0 fail:0 skip:2
> 8
> skl-i7k-
> 2 total:192 pass:166 dwarn:1 dfail:0 fail:0 skip:25
> skl-
> nuci5 total:192 pass:181 dwarn:0 dfail:0 fail:0 skip:1
> 1
> snb-
> dellxps total:192 pass:154 dwarn:0 dfail:0 fail:0 skip:3
> 8
> snb-
> x220t total:192 pass:154 dwarn:0 dfail:0 fail:1 skip:3
> 7
> BOOT FAILED for bsw-nuc-2
>
> Results at /archive/results/CI_IGT_test/Patchwork_1938/
>
> c438a31de88e7dc6bfe17ed0e094f9a1b08bcb94 drm-intel-nightly: 2016y-
> 04m-19d-09h-36m-00s UTC integration manifest
> a0ddc6e drm/i915/kbl: Don't WARN for expected secondary MISC IO power
> well request
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-19 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 10:00 [PATCH] drm/i915/kbl: Don't WARN for expected secondary MISC IO power well request Imre Deak
2016-04-19 10:56 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-04-19 12:38 ` Imre Deak [this message]
2016-04-21 8:12 ` [PATCH] " Patrik Jakobsson
2016-04-21 16:42 ` Imre Deak
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=1461069535.10192.17.camel@intel.com \
--to=imre.deak@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 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.