From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Some FDI related dotclock stuff
Date: Thu, 25 Feb 2016 20:15:44 +0200 [thread overview]
Message-ID: <20160225181544.GM15993@intel.com> (raw)
In-Reply-To: <20160219134503.19127.68584@emeril.freedesktop.org>
On Fri, Feb 19, 2016 at 01:45:03PM -0000, Patchwork wrote:
> == Summary ==
>
> Series 3541v1 drm/i915: Some FDI related dotclock stuff
> http://patchwork.freedesktop.org/api/1.0/series/3541/revisions/1/mbox/
>
> Test kms_flip:
> Subgroup basic-flip-vs-dpms:
> dmesg-warn -> PASS (ilk-hp8440p) UNSTABLE
> Subgroup basic-flip-vs-wf_vblank:
> pass -> FAIL (snb-x220t)
(kms_flip:6443) DEBUG: name = vblank
last_ts = 594.687318 usec
last_received_ts = 594.687142 usec
last_seq = 24682
current_ts = 594.870400 usec
current_received_ts = 594.870267 usec
current_seq = 24692
count = 44
seq_step = 10
(kms_flip:6443) CRITICAL: Test assertion failure function check_state, file kms_flip.c:692:
(kms_flip:6443) CRITICAL: Failed assertion: fabs((((double) diff.tv_usec) - usec_interflip) / usec_interflip) <= 0.005
(kms_flip:6443) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_flip:6443) CRITICAL: inter-vblank ts jitter: 0s, 183082usec
Hmm. So here it looks like the seq number says 10, but the timestamp
difference says 11. I found a few more of the same in the CI results.
This could be due to the race with even numbered vblank seq increments
that could be fixed by:
https://lists.freedesktop.org/archives/dri-devel/2015-September/090288.html
Filed a bug:
https://bugs.freedesktop.org/show_bug.cgi?id=94294
> Test kms_pipe_crc_basic:
> Subgroup read-crc-pipe-b:
> pass -> INCOMPLETE (ilk-hp8440p)
> Subgroup suspend-read-crc-pipe-a:
> dmesg-warn -> PASS (skl-i5k-2) UNSTABLE
> Subgroup suspend-read-crc-pipe-b:
> pass -> DMESG-WARN (skl-i5k-2) UNSTABLE
> Subgroup suspend-read-crc-pipe-c:
> dmesg-warn -> PASS (bsw-nuc-2)
> Test pm_rpm:
> Subgroup basic-pci-d3-state:
> dmesg-warn -> PASS (bsw-nuc-2)
> pass -> DMESG-WARN (byt-nuc)
[ 126.296996] [drm:intel_runtime_suspend [i915]] *ERROR* Unclaimed access detected prior to suspending
https://bugs.freedesktop.org/show_bug.cgi?id=94164
> Subgroup basic-rte:
> pass -> DMESG-WARN (bsw-nuc-2)
> pass -> FAIL (bdw-ultra)
https://bugs.freedesktop.org/show_bug.cgi?id=94163
> dmesg-warn -> PASS (byt-nuc) UNSTABLE
>
> bdw-nuci7 total:164 pass:153 dwarn:0 dfail:0 fail:0 skip:11
> bdw-ultra total:167 pass:152 dwarn:0 dfail:0 fail:1 skip:14
> bsw-nuc-2 total:167 pass:136 dwarn:1 dfail:0 fail:0 skip:30
> byt-nuc total:167 pass:141 dwarn:1 dfail:0 fail:0 skip:25
> hsw-gt2 total:167 pass:156 dwarn:0 dfail:0 fail:1 skip:10
> ilk-hp8440p total:163 pass:114 dwarn:0 dfail:0 fail:1 skip:47
> ivb-t430s total:167 pass:152 dwarn:0 dfail:0 fail:1 skip:14
> skl-i5k-2 total:167 pass:150 dwarn:1 dfail:0 fail:0 skip:16
> snb-dellxps total:167 pass:144 dwarn:0 dfail:0 fail:1 skip:22
> snb-x220t total:167 pass:143 dwarn:0 dfail:0 fail:3 skip:21
>
> Results at /archive/results/CI_IGT_test/Patchwork_1429/
>
> 631053ba117c294f0cdfe704718a040b4406a240 drm-intel-nightly: 2016y-02m-17d-21h-05m-38s UTC integration manifest
> beb6d5046d6b0eafd0aa4bc15a87e534e3e0aa8e drm/i915: Try to fix CRT port clock limits
> c7f53fb3c57d5a91216c037d757876e3a692ae0e drm/i915: Read out VGA dotclock properly on LPT
> 3c2e8606fb856686e2fa84b10f1c22ef2d209e17 drm/i915: Make the LPT iclkip 20MHz case more generic
> 6bb0fff788112afbb60391b5a77e4f62745ba0f7 drm/i915: Remove the SPLL==270Mhz assumption from intel_fdi_link_freq()
> f8260170eff5e4763d1c99e1baa3246f19c294d5 drm/i915: Move the encoder vs. FDI dotclock check out from encoder .get_config()
> 865134f99bff4ba3a91d2703282aa16c83d8ce52 drm/i915: Dump ddi_pll_sel in hex instead of decimal on HSW/BDW
--
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-02-25 18:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 19:41 [PATCH 0/6] drm/i915: Some FDI related dotclock stuff ville.syrjala
2016-02-17 19:41 ` [PATCH 1/6] drm/i915: Dump ddi_pll_sel in hex instead of decimal on HSW/BDW ville.syrjala
2016-02-18 13:19 ` Imre Deak
2016-02-17 19:41 ` [PATCH 2/6] drm/i915: Move the encoder vs. FDI dotclock check out from encoder .get_config() ville.syrjala
2016-02-18 18:18 ` Imre Deak
2016-02-17 19:41 ` [PATCH 3/6] drm/i915: Remove the SPLL==270Mhz assumption from intel_fdi_link_freq() ville.syrjala
2016-02-18 18:28 ` Imre Deak
2016-02-17 19:41 ` [PATCH 4/6] drm/i915: Make the LPT iclkip 20MHz case more generic ville.syrjala
2016-02-19 13:54 ` Zanoni, Paulo R
2016-02-19 14:04 ` Imre Deak
2016-02-17 19:41 ` [PATCH 5/6] drm/i915: Read out VGA dotclock properly on LPT ville.syrjala
2016-02-19 14:17 ` Imre Deak
2016-02-17 19:41 ` [PATCH 6/6] drm/i915: Try to fix CRT port clock limits ville.syrjala
2016-02-19 14:58 ` Imre Deak
2016-02-19 13:45 ` ✗ Fi.CI.BAT: failure for drm/i915: Some FDI related dotclock stuff Patchwork
2016-02-25 18:15 ` Ville Syrjälä [this message]
2016-03-01 11:13 ` [PATCH 0/6] " 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=20160225181544.GM15993@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;
as well as URLs for NNTP newsgroup(s).