Created attachment 132786 [details] result.log The following test fail on BYT with latest configuration ==================================================== Test list ==================================================== igt@gem_reloc_vs_gpu@faulting-reloc-interruptible igt@gem_reloc_vs_gpu@forked igt@gem_reloc_vs_gpu@forked-faulting-reloc igt@gem_reloc_vs_gpu@forked-faulting-reloc-thrashing igt@gem_reloc_vs_gpu@forked-hang igt@gem_reloc_vs_gpu@forked-interruptible igt@gem_reloc_vs_gpu@forked-interruptible-faulting-reloc igt@gem_reloc_vs_gpu@forked-interruptible-thrash-inactive igt@gem_reloc_vs_gpu@forked-thrashing igt@gem_reloc_vs_gpu@interruptible ==================================================== Graphic Stack ==================================================== Component: drm tag: libdrm-2.4.81-31-g23e234a commit: 23e234a3503f51b9d9c585123d33b936f522808d Component: cairo tag: 1.15.6-2-g57b4050 commit: 57b40507dda3f58dfc8635548d606b86dc7bcf51 Component: intel-gpu-tools tag: intel-gpu-tools-1.19-96-gfb1ddc4 commit: fb1ddc47003ad6a683db79beeb81b6cbab1feb7c Component: piglit tag: piglit-v1 commit: 56e7e5583cd4a3ca15a8cda154d46d168959dd25 ====================================== Hardware ====================================== motherboard model : ................................. motherboard id : DN2820FYK form factor : Desktop manufacturer : ................................. cpu family : Celeron cpu family id : 6 cpu information : Intel(R) Celeron(R) CPU N2830 @ 2.16GHz gpu card : Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) (prog-if 00 [VGA controller]) memory ram : 7.66 GB max memory ram : 8 GB cpu thread : 2 cpu core : 2 cpu model : 55 cpu stepping : 8 socket : <OUT OF SPEC> signature : Type 0, Family 6, Model 55, Stepping 8 hard drive : 111GiB (120GB) current cd clock frequency : 266667 kHz maximum cd clock frequency : 400000 kHz displays connected : HDMI-A-1
Created attachment 132787 [details] kern.log
Created attachment 132788 [details] dmesg.log
Adding tag into "Whiteboard" field - ReadyForDev *Status is correct *Platform is included *Feature is included *Priority and Severity correctly set *Logs included
commit edf9f2d31231c6ae2a4e621ef67c68758ddc447d Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Jul 21 15:50:36 2017 +0100 drm/i915: Only skip updating execobject.offset after error I was being overly paranoid in not updating the execobject.offset after performing the fallback copy where we set reloc.presumed_offset to -1. The thinking was to ensure that a subsequent NORELOC execbuf would be forced to process the invalid relocations. However this is overkill so long as we *only* update the execobject.offset following a successful update of the relocation value witin the batch. If we have to repeat the execbuf due to a later interruption, then we may skip the relocations on the second pass (honouring NORELOC) since the execobject.offset match the actual offsets (even though reloc.presumed_offset is garbage). Subsequent calls to execbuf with NORELOC should themselves ensure that the reloc.presumed_offset have been corrected in case of future migration. Reporting back the actual execobject.offset, even when reloc.presumed_offset is garbage, ensures that reuse of those objects use the latest information to avoid relocations. Fixes: 2889caa92321 ("drm/i915: Eliminate lots of iterations over the execobjects array") Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101635 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20170721145037.25105-4-chris@chris-wilson.co.uk Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.