Kernel: 3.17-rc5 (drm-intel-next-queued) HEAD-Commit hash: 9d34570b5dae6c0c389d6a99dbc52b62beef25b2 Platform: bwtm2 OS: Google ChromiumOS $cat /sys/kernel/debug/dri/0/i915_wa_registers Workarounds applied: 6 0xE4F0: 0x01200120, mask: 0x00000120, read: 0xffff0000, status: FAIL 0xE4F4: 0x00010001, mask: 0x00000001, read: 0xffff0000, status: FAIL 0xE184: 0x00020002, mask: 0x00000002, read: 0x00000000, status: FAIL 0x7300: 0x00100010, mask: 0x00000010, read: 0x00000000, status: FAIL 0x7004: 0x00400040, mask: 0x00000040, read: 0x000001c0, status: OK 0x7008: 0x02800200, mask: 0x00000200, read: 0x00000200, status: OK When trying to execute the above command, I get different results everytime.
Created attachment 108834 [details] [review] drm/i915: Wait thread status on gen8+ fw sequence
igt/tests/gem_workarounds --run-subtest=read should have a mechanism in place to force context to get loaded before these values are read. Alternative is to try the patch attached. The problem is that rc6 exit on bdw, is not enough to guarantee consistent access to the context which these values are part of.
gem_workarounds read is working well and reason got explained. Let's close this for now.
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.