Re: ✗ Fi.CI.BAT: failure for lib: Ask the kernel to quiesce the GPU (rev4)

From: Chris Wilson <chris@chris-wilson.co.uk>
To: Patchwork <patchwork@emeril.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for lib: Ask the kernel to quiesce the GPU (rev4)
Date: Fri, 08 Dec 2017 20:57:55 +0000	[thread overview]
Message-ID: <151276667563.16951.7538016566944767220@mail.alporthouse.com> (raw)
In-Reply-To: <20171208203133.16648.9585@emeril.freedesktop.org>

Quoting Patchwork (2017-12-08 20:31:33)
> == Series Details ==
> 
> Series: lib: Ask the kernel to quiesce the GPU (rev4)
> URL   : https://patchwork.freedesktop.org/series/31850/
> State : failure
> 
> == Summary ==
> 
> IGT patchset tested on top of latest successful build
> 37339e7171ee0bd6b45abf8cfef593ed9d8bf750 lib: Print other clients when DRM_SET_MASTER fails
> 
> with latest DRM-Tip kernel build CI_DRM_3486
> 3e49efc6d2d7 drm-tip: 2017y-12m-08d-18h-21m-46s UTC integration manifest
> 
> No testlist changes.
> 
> Test gem_mmap_gtt:
>         Subgroup basic-small-bo-tiledx:
>                 pass       -> FAIL       (fi-gdg-551) fdo#102575
> Test gem_sync:
>         Subgroup basic-all:
>                 pass       -> DMESG-FAIL (fi-blb-e6850)
>                 pass       -> FAIL       (fi-pnv-d510)

Finally some information to use. TLB failure? It's just walked off the
end of the batch. The batch hasn't moved so where is the stale data
coming from? (It's just a batch container MI_BATCH_BUFFER_END.)
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx