From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Fix oops in vlv_force_pll_on()
Date: Tue, 19 Apr 2016 14:39:55 +0300 [thread overview]
Message-ID: <20160419113955.GM4329@intel.com> (raw)
In-Reply-To: <20160419062703.20308.35776@emeril.freedesktop.org>
On Tue, Apr 19, 2016 at 06:27:03AM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Fix oops in vlv_force_pll_on()
> URL : https://patchwork.freedesktop.org/series/5888/
> State : failure
>
> == Summary ==
>
> Series 5888v1 drm/i915: Fix oops in vlv_force_pll_on()
> http://patchwork.freedesktop.org/api/1.0/series/5888/revisions/1/mbox/
>
> Test gem_busy:
> Subgroup basic-blt:
> pass -> SKIP (bsw-nuc-2)
> Test kms_flip:
> Subgroup basic-flip-vs-wf_vblank:
> pass -> FAIL (snb-x220t)
(kms_flip:6637) DEBUG: name = vblank
last_ts = 654.650667 usec
last_received_ts = 654.650261 usec
last_seq = 1067
current_ts = 654.834652 usec
current_received_ts = 654.834207 usec
current_seq = 1077
count = 33
seq_step = 10
(kms_flip:6637) CRITICAL: Test assertion failure function check_state, file kms_flip.c:692:
(kms_flip:6637) CRITICAL: Failed assertion: fabs((((double) diff.tv_usec) - usec_interflip) / usec_interflip) <= 0.005
(kms_flip:6637) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_flip:6637) CRITICAL: inter-vblank ts jitter: 0s, 183985usec
> pass -> FAIL (bsw-nuc-2)
(kms_flip:6946) DEBUG: name = flip
last_ts = 715.98251 usec
last_received_ts = 715.98432 usec
last_seq = 27228
current_ts = 715.281678 usec
current_received_ts = 715.282796 usec
current_seq = 27238
count = 101
seq_step = 1
(kms_flip:6946) CRITICAL: Test assertion failure function check_state, file kms_flip.c:692:
(kms_flip:6946) CRITICAL: Failed assertion: fabs((((double) diff.tv_usec) - usec_interflip) / usec_interflip) <= 0.005
(kms_flip:6946) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_flip:6946) CRITICAL: inter-flip ts jitter: 0s, 183427usec
https://bugs.freedesktop.org/show_bug.cgi?id=94294
> Test kms_force_connector_basic:
> Subgroup force-load-detect:
> skip -> PASS (snb-x220t)
> Test kms_pipe_crc_basic:
> Subgroup hang-read-crc-pipe-b:
> pass -> INCOMPLETE (snb-dellxps)
Sigh.
>
> bdw-nuci7 total:192 pass:180 dwarn:0 dfail:0 fail:0 skip:12
> bdw-ultra total:192 pass:169 dwarn:0 dfail:0 fail:0 skip:23
> bsw-nuc-2 total:191 pass:150 dwarn:0 dfail:0 fail:1 skip:40
> byt-nuc total:191 pass:153 dwarn:0 dfail:0 fail:0 skip:38
> hsw-brixbox total:192 pass:168 dwarn:0 dfail:0 fail:0 skip:24
> ivb-t430s total:192 pass:164 dwarn:0 dfail:0 fail:0 skip:28
> skl-i7k-2 total:192 pass:167 dwarn:0 dfail:0 fail:0 skip:25
> skl-nuci5 total:192 pass:181 dwarn:0 dfail:0 fail:0 skip:11
> snb-dellxps total:9 pass:7 dwarn:0 dfail:0 fail:0 skip:1
> snb-x220t total:192 pass:153 dwarn:0 dfail:0 fail:2 skip:37
>
> Results at /archive/results/CI_IGT_test/Patchwork_1935/
>
> b1b2678f7bf90de8cecba84acb8f8c967a5f5d80 drm-intel-nightly: 2016y-04m-18d-17h-17m-00s UTC integration manifest
> a67b76f drm/i915: Fix oops in vlv_force_pll_on()
--
Ville Syrjälä
Intel OTC
_______________________________________________
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 11:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 17:34 [PATCH] drm/i915: Fix oops in vlv_force_pll_on() ville.syrjala
2016-04-19 6:27 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-04-19 11:39 ` Ville Syrjälä [this message]
2016-04-19 10:02 ` [PATCH] " Marius Vlad
2016-04-19 11:25 ` Jani Nikula
2016-04-19 12:01 ` Ville Syrjälä
2016-04-20 13:19 ` Daniel Vetter
2016-04-20 13:47 ` Ville Syrjälä
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=20160419113955.GM4329@intel.com \
--to=ville.syrjala@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