[Intel-gfx] ✗ Fi.CI.BAT: warning for FBC crtc/fb locking + smaller fixes
Zanoni, Paulo R
paulo.r.zanoni at intel.com
Thu Jan 21 12:14:34 PST 2016
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/
>
More information about the Intel-gfx
mailing list