Bug 80592 - stuck on render/blitter ring
Summary: stuck on render/blitter ring
Status: CLOSED DUPLICATE of bug 54226
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Paulo Zanoni
QA Contact: Intel GFX Bugs mailing list
Depends on:
Reported: 2014-06-27 11:36 UTC by jens+freedesktop
Modified: 2017-07-24 22:53 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

GPU crash dump (2.06 MB, text/plain)
2014-06-27 11:36 UTC, jens+freedesktop
no flags Details
dmesg (the relevant stuff is near the end) (110.21 KB, text/plain)
2014-06-27 11:38 UTC, jens+freedesktop
no flags Details
syslog (relevant stuff at around 13:15) (92.10 KB, text/plain)
2014-06-27 11:39 UTC, jens+freedesktop
no flags Details
Xorg log (54.08 KB, text/plain)
2014-06-27 11:40 UTC, jens+freedesktop
no flags Details

Description jens+freedesktop 2014-06-27 11:36:57 UTC
Created attachment 101859 [details]
GPU crash dump

My dmesg told me to file a new bug, so here it goes:

A few minutes ago, my display froze completely. It came back to life a few seconds later, but any movement on the display lagged terribly afterwards. After I restarted X (not my entire system), everything was back to normal.
Syslog, dmesg, Xorg log and gpu crash dump are attached. If you need any more information, please let me know.
Note that I can NOT easily test development versions of any software as this happened on a production system.
Comment 1 jens+freedesktop 2014-06-27 11:38:16 UTC
Created attachment 101860 [details]
dmesg (the relevant stuff is near the end)
Comment 2 jens+freedesktop 2014-06-27 11:39:32 UTC
Created attachment 101861 [details]
syslog (relevant stuff at around 13:15)
Comment 3 jens+freedesktop 2014-06-27 11:40:10 UTC
Created attachment 101862 [details]
Xorg log
Comment 4 Chris Wilson 2014-06-27 11:40:37 UTC

*** This bug has been marked as a duplicate of bug 54226 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.