<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - GPU crash dump (Asus Notebook, Intel GMA 4500)" href="https://bugs.freedesktop.org/show_bug.cgi?id=90603#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - GPU crash dump (Asus Notebook, Intel GMA 4500)" href="https://bugs.freedesktop.org/show_bug.cgi?id=90603">bug 90603</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>Any other symptoms? That gpu error should have been non-fatal and I believe is finally fixed by commit 983d308cb8f602d1920a8c40196eb2ab6cc07bd2 Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Date: Mon Jan 26 10:47:10 2015 +0000 agp/intel: Serialise after GTT updates An interesting bug occurs on Pineview through which the root cause is that the writes of the PTE values into the GTT is not serialised with subsequent memory access through the GTT (when using WC updates of the PTE values). This is despite there being a posting read after the GTT update. However, by changing the address of the posting read, the memory access is indeed serialised correctly. Whilst we are manipulating the memory barriers, we can remove the compiler :memory restraint on the intermediate PTE writes knowing that we explicitly perform a posting read afterwards. v2: Replace posting reads with explicit write memory barriers - in particular this is advantages in case of single page objects. Update comments to mention this issue is only with WC writes.</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> <li>You are the assignee for the bug.</li> </ul> </body> </html>