<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - Ubuntu 12.4 crash gpu" href="https://bugs.freedesktop.org/show_bug.cgi?id=73276#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - Ubuntu 12.4 crash gpu" href="https://bugs.freedesktop.org/show_bug.cgi?id=73276">bug 73276</a> from <a class="email" href="mailto:rakothedin@gmail.com" title="Hohahiu <rakothedin@gmail.com>"> Hohahiu</a> <pre>(In reply to <a href="show_bug.cgi?id=73276#c11">comment #11</a>) > (In reply to <a href="show_bug.cgi?id=73276#c7">comment #7</a>) > > I have a similar error in dmesg while using kernel 3.13.0 and earlier rc > > versions: > > Oh no you don't! In fact you have <a class="bz_bug_link bz_status_NEW " title="NEW --- - [hsw ult] first few megabytes of aperture space overwritten after i915.ko loads and before userspace submits first batch" href="show_bug.cgi?id=73261">bug 73261</a>, So should I attach all these files to those bug report? Mine kernel version and GPU seems to be different. Also I didn't have this error message while using 3.12: [ 51.015929] [drm] stuck on render ring [ 51.015937] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 51.015939] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 51.015940] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 51.015941] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 51.015942] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.</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>