<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [SNB] igt@drv_module_reload@basic-reload-final fails and hard hangs the system" href="https://bugs.freedesktop.org/show_bug.cgi?id=100858#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [SNB] igt@drv_module_reload@basic-reload-final fails and hard hangs the system" href="https://bugs.freedesktop.org/show_bug.cgi?id=100858">bug 100858</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>The answer lies in if the GPU didn't write the dword to where we wanted, where did it write it? And the same worrying question will be for lots of different ops. The HWS is intact otherwise it would have complained about a gpu hang... Actually no, that test isn't checking so that's a more reasonable explanation that the HWS write also went astray, i.e. it is likely that nothing is right in the way the GPU is addressing memory. In load/unload we do a GPU reset, so everything should be sane... Remove the store dword check and see it it still hard hangs. If so, we can start removing chunks from the load/unload sequence and see at what point it works.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>