[ 609.719934] Partial view for 3739  (offset=3584, size=256 [256, row size 0], fence=-1, tiling=0, stride=0) misalignment, expected write to page (3739 + 0 [0xe9b000]) of 0xe9b, found 0xc31e7b
[ 609.720094] i915/i915_gem_object_live_selftests: igt_partial_tiling failed with error -22
[ 609.956121] i915: probe of 0000:00:02.0 failed with error -22
Setting to high since it affects CNL and ICL, but it only affects one test, so no need to go to highest.
It's a pretty severe failure. That reading from the gtt is broken may impact virtually any test if the timing is against us. More interesting is the coherency results, which suggest that we need to mark cnl+ as having an incoherent gtt.
commit 21eb1850fa0bd0a9b729bf3708da78888433027f (HEAD -> drm-intel-next-queued, drm-intel/for-linux-next, drm-intel/drm-intel-next-queued)
Author: Chris Wilson <firstname.lastname@example.org>
Date: Wed Aug 1 11:47:21 2018 +0100
drm/i95: Mark GGTT as incoherent for gen10+
The evidence suggests that we need to start treating writes via GGTT as
incoherent for gen10+, that is that they are internally buffered and not
immediately visible via a read along a different physical path.
Signed-off-by: Chris Wilson <email@example.com>
Cc: Mika Kuoppala <firstname.lastname@example.org>
Reviewed-by: Mika Kuoppala <email@example.com>