| Summary: |
Google Hangouts video with Chrome caused "stuck on render ring" |
| Product: |
DRI
|
Reporter: |
bugzilla |
| Component: |
DRM/Intel | Assignee: |
Paulo Zanoni <przanoni> |
| Status: |
CLOSED
DUPLICATE
|
QA Contact: |
Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: |
normal
|
|
|
| Priority: |
medium
|
CC: |
bugzilla, intel-gfx-bugs
|
| Version: |
unspecified | |
|
| Hardware: |
x86-64 (AMD64) | |
|
| OS: |
Linux (All) | |
|
| Whiteboard: |
|
|
i915 platform:
|
|
i915 features:
|
|
|---|
| Attachments: |
|
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.
Created attachment 100942 [details] Contents of /sys/class/drm/card0/error While on a Google Hangouts video call, Chrome locked up and the video froze. Chrome had to be killed, and the following appeared in the syslog: Jun 12 13:33:34 kernel: [150622.222686] [drm] stuck on render ring Jun 12 13:33:34 kernel: [150622.222691] [drm] GPU crash dump saved to /sys/class/drm/card0/error Jun 12 13:33:34 kernel: [150622.222692] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Jun 12 13:33:34 kernel: [150622.222693] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Jun 12 13:33:34 kernel: [150622.222694] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Jun 12 13:33:34 kernel: [150622.222695] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. I'm running Ubuntu 14.04, with Ivy Bridge integrated graphics.