<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [ilk] Batch buffer corruption" href="https://bugs.freedesktop.org/show_bug.cgi?id=83564#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [ilk] Batch buffer corruption" href="https://bugs.freedesktop.org/show_bug.cgi?id=83564">bug 83564</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to <a href="show_bug.cgi?id=83564#c4">comment #4</a>) > OK, the sources were actually in xserver-xorg-video-intel (not xf86-). As you doing so well, you could actually use the upstream code: <a href="http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/">http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/</a> (more bug fixes, more debugging code) > Results: > - No output on the GDB console. > - Same or similar error messages in /var/log/syslog (I saved syslog and the > new crash dump, I can post them here if needed). > - after 30-40 seconds I get "*ERROR* context hanging too fast, declaring > banned!" in the system log and the GUI seems to come back to life, but not > really working. > > Anyway, at least I have the sources compiling and I can take a stab at > getting familiar with them. I will also get the Linux kernel source and see > if I can add some printk()s to see on which exact commands from userland > trigger the errors. If you have any better ideas, let me know. Don't worry about instrumenting the kernel, it is already providing you with enough information to incriminate userspace...</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>