From: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
To: "Lespiau, Damien" <damien.lespiau@intel.com>,
"Vetter, Daniel" <daniel.vetter@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ Fi.CI.BAT: warning for FBC crtc/fb locking + smaller fixes
Date: Thu, 21 Jan 2016 20:14:34 +0000 [thread overview]
Message-ID: <1453407273.22174.131.camel@intel.com> (raw)
In-Reply-To: <20160119145000.31154.29052@annarchy.freedesktop.org>
Em Ter, 2016-01-19 às 14:50 +0000, Patchwork escreveu:
> == Summary ==
>
> Built on 20c388faff9d8c41ab27e825c685526561b892a2 drm-intel-nightly:
> 2016y-01m-19d-13h-31m-46s UTC integration manifest
>
> Test kms_flip:
> Subgroup basic-flip-vs-modeset:
> pass -> DMESG-WARN (skl-i5k-2)
The dmesg warn is the following:
[ 273.515394] [drm:gen8_irq_handler [i915]] *ERROR* The master control
interrupt lied (DE PIPE)!
I coulnd't find anything showing that this error was present before the
patch series, but I also can't reproduce it on my SKL machine and I
find it hard to believe that this error was introduced by any of the
patches in question.
So, with the new rules, how do I proceed here?
If the series was shorter I'd just resubmit and see if the RNG allows
me to pass, but sending 25 patches again won't be cool. It would be
good to have a way to ask the CI to run the failed subtests again on
the same patch series in order to confirm things.
>
> bdw-
> nuci7 total:140 pass:131 dwarn:0 dfail:0 fail:0 skip:9
>
> bsw-nuc-
> 2 total:143 pass:117 dwarn:2 dfail:0 fail:0 skip:24
> byt-
> nuc total:143 pass:125 dwarn:3 dfail:0 fail:0 skip:1
> 5
> hsw-
> brixbox total:143 pass:136 dwarn:0 dfail:0 fail:0 skip:7
>
> hsw-
> gt2 total:143 pass:139 dwarn:0 dfail:0 fail:0 skip:4
>
> ilk-
> hp8440p total:143 pass:102 dwarn:3 dfail:0 fail:0 skip:3
> 8
> ivb-
> t430s total:137 pass:124 dwarn:3 dfail:4 fail:0 skip:6
>
> skl-i5k-
> 2 total:143 pass:132 dwarn:3 dfail:0 fail:0 skip:8
> snb-
> dellxps total:143 pass:124 dwarn:5 dfail:0 fail:0 skip:1
> 4
> snb-
> x220t total:143 pass:124 dwarn:5 dfail:0 fail:1 skip:1
> 3
>
> Results at /archive/results/CI_IGT_test/Patchwork_1221/
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-01-21 20:14 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 13:35 [PATCH 00/25] FBC crtc/fb locking + smaller fixes Paulo Zanoni
2016-01-19 13:35 ` [PATCH 01/25] drm/i915/fbc: wait for a vblank instead of 50ms when enabling Paulo Zanoni
2016-01-21 14:17 ` Maarten Lankhorst
2016-01-21 16:56 ` Zanoni, Paulo R
2016-01-21 20:03 ` Paulo Zanoni
2016-01-25 13:32 ` Zanoni, Paulo R
2016-01-26 17:44 ` Rodrigo Vivi
2016-01-26 18:08 ` Zanoni, Paulo R
2016-01-29 0:07 ` Rodrigo Vivi
2016-01-29 20:42 ` Zanoni, Paulo R
2016-01-19 13:35 ` [PATCH 02/25] drm/i915/fbc: extract intel_fbc_can_activate() Paulo Zanoni
2016-01-21 11:35 ` Maarten Lankhorst
2016-01-21 12:06 ` Zanoni, Paulo R
2016-01-19 13:35 ` [PATCH 03/25] drm/i915/fbc: extract intel_fbc_can_enable() Paulo Zanoni
2016-01-19 13:35 ` [PATCH 04/25] drm/i915/fbc: introduce struct intel_fbc_reg_params Paulo Zanoni
2016-01-21 12:48 ` Maarten Lankhorst
2016-01-21 12:54 ` Zanoni, Paulo R
2016-01-19 13:35 ` [PATCH 05/25] drm/i915/fbc: replace frequent dev_priv->fbc.x with fbc->x Paulo Zanoni
2016-01-19 13:35 ` [PATCH 06/25] drm/i915/fbc: don't use the frontbuffer tracking subsystem for flips Paulo Zanoni
2016-01-19 13:35 ` [PATCH 07/25] drm/i915/fbc: don't flush for operations on the wrong frontbuffer Paulo Zanoni
2016-01-19 13:35 ` [PATCH 08/25] drm/i915/fbc: unconditionally update FBC during atomic commits Paulo Zanoni
2016-01-19 14:09 ` kbuild test robot
2016-01-21 13:04 ` Maarten Lankhorst
2016-01-21 13:27 ` Zanoni, Paulo R
2016-01-21 13:32 ` Maarten Lankhorst
2016-01-21 20:07 ` Paulo Zanoni
2016-01-19 13:35 ` [PATCH 09/25] drm/i915/fbc: introduce struct intel_fbc_state_cache Paulo Zanoni
2016-01-19 13:35 ` [PATCH 10/25] drm/i915/fbc: split intel_fbc_update into pre and post update Paulo Zanoni
2016-01-19 13:35 ` [PATCH 11/25] drm/i915/fbc: fix the FBC state checking code Paulo Zanoni
2016-08-15 20:55 ` Chris Wilson
2016-08-15 22:47 ` Zanoni, Paulo R
2016-08-16 7:36 ` chris
2016-01-19 13:35 ` [PATCH 12/25] drm/i915/fbc: unexport intel_fbc_deactivate Paulo Zanoni
2016-01-19 13:35 ` [PATCH 13/25] drm/i915/fbc: rename the FBC disable functions Paulo Zanoni
2016-01-19 13:35 ` [PATCH 14/25] drm/i915/fbc: make sure we cancel the work function at fbc_disable Paulo Zanoni
2016-01-19 13:35 ` [PATCH 15/25] drm/i915/fbc: rewrite the multiple_pipes_ok() code for locking Paulo Zanoni
2016-01-21 13:29 ` Maarten Lankhorst
2016-01-19 13:35 ` [PATCH 16/25] drm/i915: simplify struct drm_device access at intel_atomic_check() Paulo Zanoni
2016-01-19 13:35 ` [PATCH 17/25] drm/i915/fbc: choose the new FBC CRTC during atomic check Paulo Zanoni
2016-01-19 13:35 ` [PATCH 18/25] drm/i915/fbc: move intel_fbc_{enable, disable} call one level up Paulo Zanoni
2016-01-19 13:35 ` [PATCH 19/25] drm/i915/fbc: make FBC work with fastboot Paulo Zanoni
2016-01-19 13:35 ` [PATCH 20/25] drm/i915/fbc: don't try to deactivate FBC if it's not enabled Paulo Zanoni
2016-01-19 13:35 ` [PATCH 21/25] drm/i915/fbc: don't print no_fbc_reason to dmesg Paulo Zanoni
2016-01-19 13:35 ` [PATCH 22/25] drm/i915/fbc: don't store the fb_id on reg_params Paulo Zanoni
2016-01-19 13:35 ` [PATCH 23/25] drm/i915/fbc: call intel_fbc_pre_update earlier during page flips Paulo Zanoni
2016-01-19 13:35 ` [PATCH 24/25] drm/i915/fbc: don't store/check a pointer to the FB Paulo Zanoni
2016-01-19 13:35 ` [PATCH 25/25] drm/i915/fbc: refactor some small functions called only once Paulo Zanoni
2016-01-19 14:50 ` ✗ Fi.CI.BAT: warning for FBC crtc/fb locking + smaller fixes Patchwork
2016-01-21 20:14 ` Zanoni, Paulo R [this message]
2016-01-22 11:28 ` Damien Lespiau
2016-01-25 16:26 ` Daniel Vetter
2016-01-21 14:17 ` [PATCH 00/25] " Maarten Lankhorst
2016-01-22 8:01 ` ✗ Fi.CI.BAT: failure for FBC crtc/fb locking + smaller fixes (rev3) Patchwork
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=1453407273.22174.131.camel@intel.com \
--to=paulo.r.zanoni@intel.com \
--cc=damien.lespiau@intel.com \
--cc=daniel.vetter@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