<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [BAT][HSW] igt@tools_test@tools_test - Unclaimed read from register 0x[4c]400c" href="https://bugs.freedesktop.org/show_bug.cgi?id=102543#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [BAT][HSW] igt@tools_test@tools_test - Unclaimed read from register 0x[4c]400c" href="https://bugs.freedesktop.org/show_bug.cgi?id=102543">bug 102543</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>commit d7a133d886b45651e36e7065998b1413d379ac1f Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Date: Thu Sep 7 14:44:41 2017 +0100 drm/i915: Disable mmio debugging during user access If the user bypasses i915 and accesses mmio directly, that easily confuses our automatic mmio debugging (any error we then detect is likely to be as a result of the user). Since we expect userspace to open debugfs/i915_forcewake_user if i915.ko is loaded and they want mmio access, that makes the opportune time to disable our debugging for duration of the bypass. v2: Move the fiddling of uncore internals to uncore.c The issue in intel_reg_dump is still there, just not triggering a kernel warning.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>