[Intel-gfx] ✗ Fi.CI.IGT: warning for GuC based reset engine

Michel Thierry michel.thierry at intel.com
Tue Oct 31 20:56:03 UTC 2017


On 10/31/2017 3:20 AM, Chris Wilson wrote:
> Quoting Patchwork (2017-10-30 23:20:13)
>> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_6267/shards.html
> 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_6267/shard-kbl1/igt@prime_busy@wait-hang-render.html
> is suspicious.
> -Chris
> 

It is suspicious (I just double checked that prime_busy runs fine in my 
skl). I don't know if the log is complete or it was killed before 
starting the subtest. Instead of:
[  ] [IGT] prime_busy: executing
[  ] [IGT] prime_busy: starting subtest wait-hang-render

the log only has:

<7>[   59.430514] [IGT] kms_plane_lowres: exiting, ret=77
<7>[   59.522502] [IGT] prime_busy: executing
������������������������������

(and a few tests were returning EBADFD).


More information about the Intel-gfx mailing list