On Fri, Mar 03, 2017 at 08:19:43AM -0000, Patchwork wrote: > == Series Details == > > Series: drm/i915: Always wakeup the next breadcrumb waiter (rev3) > URL : https://patchwork.freedesktop.org/series/20590/ > State : failure > > == Summary == > > Series 20590v3 drm/i915: Always wakeup the next breadcrumb waiter > https://patchwork.freedesktop.org/api/1.0/series/20590/revisions/3/mbox/ > > Test drv_module_reload: > Subgroup basic-reload: > dmesg-warn -> PASS (fi-ilk-650) > Test gem_exec_flush: > Subgroup basic-batch-kernel-default-uc: > fail -> PASS (fi-snb-2600) fdo#100007 > Test gem_exec_parallel: > Subgroup basic: > pass -> FAIL (fi-bxt-t5700) > pass -> FAIL (fi-skl-6260u) > pass -> FAIL (fi-bxt-j4205) > pass -> FAIL (fi-bdw-5557u) > pass -> FAIL (fi-skl-6700hq) > pass -> FAIL (fi-kbl-7500u) > Test gem_sync: > Subgroup basic-store-all: > pass -> FAIL (fi-bxt-t5700) > pass -> FAIL (fi-bxt-j4205) > pass -> FAIL (fi-kbl-7500u) > pass -> FAIL (fi-skl-6260u) > pass -> FAIL (fi-skl-6700hq) > pass -> FAIL (fi-bdw-5557u) > pass -> FAIL (fi-skl-6700k) > pass -> FAIL (fi-skl-6770hq) > pass -> FAIL (fi-bsw-n3050) Clearly I missed some reason as to why that wakeup *is* required. We are not as serialised by the spinlock as I thought? -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
