[Bug 78362] New: stuck on render ring
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue May 6 15:59:50 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=78362
Priority: medium
Bug ID: 78362
CC: intel-gfx-bugs at lists.freedesktop.org
Assignee: intel-gfx-bugs at lists.freedesktop.org
Summary: stuck on render ring
QA Contact: intel-gfx-bugs at lists.freedesktop.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: ryllu800proar at byom.de
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: DRM/Intel
Product: DRI
Created attachment 98592
--> https://bugs.freedesktop.org/attachment.cgi?id=98592&action=edit
GPU crash dump
It's an Acer C720 Chromebook running Arch Linux x86_64.
dmesg's last lines:
[ 5168.242205] perf samples too long (2507 > 2500), lowering
kernel.perf_event_max_sample_rate to 50100
[13802.523971] perf samples too long (5000 > 4990), lowering
kernel.perf_event_max_sample_rate to 25200
[13924.032406] [drm] stuck on render ring
[13924.032425] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[13924.032430] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[13924.032434] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[13924.032438] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[13924.032442] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140506/ad45f5e2/attachment.html>
More information about the intel-gfx-bugs
mailing list