Summary: |
Chromium sometimes causes drm to crash |
Product: |
DRI
|
Reporter: |
Lorenz <lorenz-dev> |
Component: |
DRM/Intel | Assignee: |
Daniel Vetter <daniel> |
Status: |
CLOSED
DUPLICATE
|
QA Contact: |
Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: |
normal
|
|
|
Priority: |
medium
|
CC: |
intel-gfx-bugs, lorenz-dev
|
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 100302 [details] GPU crash dump Happened to me once before (with Chromium 34), and again today (Chromium 35.0.1916.114 Debian jessie/sid (270117)). I was reading a long webpage and scrolling when the picture became stuck for a few seconds. Chromium did not recover. I am using Debian unstable with Linux 3.14.5 (self-built), libdrm-intel1 2.4.54-1, Xorg 1:7.7+7. If you need any further information, I'd be happy to help. dmesg: [16139.620025] [drm] stuck on render ring [16139.620028] [drm] GPU crash dump saved to /sys/class/drm/card0/error [16139.620029] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [16139.620030] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [16139.620030] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [16139.620031] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.