Quoting Patchwork (2018-06-14 23:53:30)
> == Series Details ==
> 
> Series: drm/i915: Enable provoking vertex fix on Gen9+ systems.
> URL   : https://patchwork.freedesktop.org/series/44781/
> State : failure
> 
> == Summary ==
> 
> = CI Bug Log - changes from CI_DRM_4322 -> Patchwork_9312 =
> 
> == Summary - FAILURE ==
> 
>   Serious unknown changes coming with Patchwork_9312 absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_9312, please notify your bug team to allow them
>   to document this new failure mode, which will reduce false positives in CI.
> 
>   External URL: 
> https://patchwork.freedesktop.org/api/1.0/series/44781/revisions/1/mbox/
> 
> == Possible new issues ==
> 
>   Here are the unknown changes that may have been introduced in 
> Patchwork_9312:
> 
>   === IGT changes ===
> 
>     ==== Possible regressions ====
> 
>     igt@gem_workarounds@basic-read:
>       fi-skl-6260u:       PASS -> FAIL
>       fi-cfl-s3:          PASS -> FAIL
>       fi-skl-6700k2:      PASS -> FAIL
>       fi-skl-6770hq:      PASS -> FAIL
>       fi-kbl-7560u:       PASS -> FAIL
>       fi-skl-6600u:       PASS -> FAIL
>       fi-bxt-dsi:         PASS -> FAIL
>       fi-kbl-guc:         PASS -> FAIL
>       fi-kbl-7500u:       PASS -> FAIL
>       fi-skl-6700hq:      PASS -> FAIL
>       fi-bxt-j4205:       PASS -> FAIL
>       fi-skl-gvtdvm:      PASS -> FAIL
>       fi-cfl-guc:         PASS -> FAIL
>       {fi-whl-u}:         PASS -> FAIL
>       fi-cfl-8700k:       PASS -> FAIL
>       fi-glk-j4005:       PASS -> FAIL
>       fi-skl-guc:         PASS -> FAIL
>       fi-kbl-7567u:       PASS -> FAIL
>       fi-kbl-r:           PASS -> FAIL

(gem_workarounds:3828) DEBUG: Address   val             mask            read    
        result
(gem_workarounds:3828) DEBUG: 0x07014   0x20002000      0x00002000      
0x00002000      OK
(gem_workarounds:3828) DEBUG: 0x0E194   0x01000100      0x00000100      
0x00000114      OK
(gem_workarounds:3828) DEBUG: 0x0E4F0   0x81008100      0x00008100      
0xFFFF8120      OK
(gem_workarounds:3828) DEBUG: 0x0E184   0x00200020      0x00000020      
0x00000022      OK
(gem_workarounds:3828) DEBUG: 0x0E194   0x00140014      0x00000014      
0x00000114      OK
(gem_workarounds:3828) DEBUG: 0x07004   0x00420042      0x00000042      
0x000029C2      OK
(gem_workarounds:3828) DEBUG: 0x0E188   0x00080000      0x00000008      
0x00008030      OK
(gem_workarounds:3828) DEBUG: 0x07300   0x80208020      0x00008020      
0x00008830      OK
(gem_workarounds:3828) DEBUG: 0x07300   0x00100010      0x00000010      
0x00008830      OK
(gem_workarounds:3828) DEBUG: 0x0E184   0x00020002      0x00000002      
0x00000022      OK
(gem_workarounds:3828) DEBUG: 0x0E180   0x20002000      0x00002000      
0x00002000      OK
(gem_workarounds:3828) DEBUG: 0x02580   0x00010000      0x00000001      
0x00000004      OK
(gem_workarounds:3828) DEBUG: 0x02580   0x00060004      0x00000006      
0x00000004      OK
(gem_workarounds:3828) WARNING: 0x02088 0x00020002      0x00000002      
0x00000000      FAIL
(gem_workarounds:3828) WARNING: 0x02090 0x10001000      0x00001000      
0x00000000      FAIL

The 2 writes didn't stick. Not context saved? Or something even more
peculiar?

(Look at all those repeated register writes, no wonder we ran out of
space.)
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Reply via email to