[Bug 87163] New: GPU hang when using Chromium
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Dec 9 09:46:25 PST 2014
https://bugs.freedesktop.org/show_bug.cgi?id=87163
Bug ID: 87163
Summary: GPU hang when using Chromium
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: bugs.freedesktop.org at wizy.org
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 110637
--> https://bugs.freedesktop.org/attachment.cgi?id=110637&action=edit
Contents of /sys/class/drm/card1/error
I'm getting GPU hangs when using Chromium.
systemd's journal reports the following, when using kernel 3.14.25:
Dec 08 17:26:14 wizylap kernel: [drm:ring_stuck] *ERROR* Kicking stuck wait on
render ring
Dec 08 17:26:14 wizylap kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Dec 08 17:26:14 wizylap kernel: [drm] GPU hangs can indicate a bug anywhere in
the entire gfx stack, including userspace.
Dec 08 17:26:14 wizylap kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
Dec 08 17:26:14 wizylap kernel: [drm] drm/i915 developers can then reassign to
the right component if it's not a kernel issue.
Dec 08 17:26:14 wizylap kernel: [drm] The gpu crash dump is required to analyze
gpu hangs, so please always attach it.
Dec 08 17:26:24 wizylap display-manager-start[2025]: (EE) [mi] EQ overflowing.
Additional events will be discarded until existing events are processed.
Dec 08 17:26:24 wizylap display-manager-start[2025]: (EE)
Dec 08 17:26:24 wizylap display-manager-start[2025]: (EE) Backtrace:
Dec 08 17:26:24 wizylap display-manager-start[2025]: (EE)
Dec 08 17:26:24 wizylap display-manager-start[2025]: (EE) [mi] These backtraces
from mieqEnqueue may point to a culprit higher up the stack.
Dec 08 17:26:24 wizylap display-manager-start[2025]: (EE) [mi] mieq is *NOT*
the cause. It is a victim.
Dec 08 17:26:24 wizylap display-manager-start[2025]: (EE) [mi] EQ overflow
continuing. 100 events have been dropped.
Dec 08 17:26:24 wizylap display-manager-start[2025]: (EE)
Dec 08 17:26:24 wizylap display-manager-start[2025]: (EE) Backtrace:
Dec 08 17:26:24 wizylap display-manager-start[2025]: (EE)
Dec 08 17:26:25 wizylap kernel: [drm:ring_stuck] *ERROR* Kicking stuck wait on
render ring
Dec 08 17:26:25 wizylap display-manager-start[2025]: [mi] Increasing EQ size to
1024 to prevent dropped events.
Dec 08 17:26:25 wizylap display-manager-start[2025]: [mi] EQ processing has
resumed after 199 dropped events.
Dec 08 17:26:25 wizylap display-manager-start[2025]: [mi] This may be caused my
a misbehaving driver monopolizing the server's resources.
Dec 08 17:26:59 wizylap kernel: [drm:ring_stuck] *ERROR* Kicking stuck wait on
render ring
When using kernel 3.17.6, systemd reports the following:
Dec 08 19:29:11 wizylap kernel: [drm] GPU HANG: ecode -1:0x00000000, reason:
Kicking stuck wait on render ring, action: continue
Dec 08 19:29:11 wizylap kernel: [drm] GPU hangs can indicate a bug anywhere in
the entire gfx stack, including userspace.
Dec 08 19:29:11 wizylap kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
Dec 08 19:29:11 wizylap kernel: [drm] drm/i915 developers can then reassign to
the right component if it's not a kernel issue.
Dec 08 19:29:11 wizylap kernel: [drm] The gpu crash dump is required to analyze
gpu hangs, so please always attach it.
Dec 08 19:29:11 wizylap kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Dec 08 19:29:21 wizylap kernel: [drm] GPU HANG: ecode -1:0x00000000, reason:
Kicking stuck wait on render ring, action: continue
Dec 08 19:42:46 wizylap kernel: [drm] GPU HANG: ecode -1:0x00000000, reason:
Kicking stuck wait on render ring, action: continue
Dec 08 19:42:54 wizylap kernel: [drm] GPU HANG: ecode -1:0x00000000, reason:
Kicking stuck wait on render ring, action: continue
Dec 08 19:44:16 wizylap kernel: [drm] GPU HANG: ecode -1:0x00000000, reason:
Kicking stuck wait on render ring, action: continue
Dec 08 19:44:30 wizylap display-manager-start[2056]: (EE) [mi] EQ overflowing.
Additional events will be discarded until existing events are processed.
Dec 08 19:44:30 wizylap display-manager-start[2056]: (EE)
Dec 08 19:44:30 wizylap display-manager-start[2056]: (EE) Backtrace:
Dec 08 19:44:30 wizylap display-manager-start[2056]: (EE)
Dec 08 19:44:30 wizylap display-manager-start[2056]: (EE) [mi] These backtraces
from mieqEnqueue may point to a culprit higher up the stack.
Dec 08 19:44:30 wizylap display-manager-start[2056]: (EE) [mi] mieq is *NOT*
the cause. It is a victim.
Dec 08 19:44:31 wizylap kernel: [drm] GPU HANG: ecode -1:0x00000000, reason:
Kicking stuck wait on render ring, action: continue
Dec 08 19:44:31 wizylap display-manager-start[2056]: [mi] Increasing EQ size to
1024 to prevent dropped events.
Dec 08 19:44:31 wizylap display-manager-start[2056]: [mi] EQ processing has
resumed after 61 dropped events.
Dec 08 19:44:31 wizylap display-manager-start[2056]: [mi] This may be caused my
a misbehaving driver monopolizing the server's resources.
Dec 08 19:45:05 wizylap kernel: [drm] GPU HANG: ecode -1:0x00000000, reason:
Kicking stuck wait on render ring, action: continue
Dec 08 19:45:05 wizylap kernel: [drm] no progress on render ring
Dec 08 19:45:05 wizylap kernel: [drm] GPU HANG: ecode -1:0x00000000, reason:
Ring hung, action: reset
Here's some more info from chrome://gpu:
Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Disabled
Rasterization: Hardware accelerated
Threaded Rasterization: Enabled
Video Decode: Hardware accelerated
Video Encode: Hardware accelerated
WebGL: Hardware accelerated
Driver Bug Workarounds
clear_uniforms_before_first_program_use
count_all_in_varyings_packing
disable_post_sub_buffers_for_onscreen_surfaces
scalarize_vec_and_mat_constructor_args
Problems Detected
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Mesa drivers in Linux handle varyings without static use incorrectly: 333885
Applied Workarounds: count_all_in_varyings_packing
Disable partial swaps on linux drivers: 339493
Applied Workarounds: disable_post_sub_buffers_for_onscreen_surfaces
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
Raster is using a single thread.
Disabled Features: multiple_raster_threads
Version Information
Data exported 12/9/2014, 6:19:37 PM
Chrome version Chrome/39.0.2171.71
Operating system Linux 3.17.6
Software rendering list version 0
Driver bug list version 7.7
ANGLE commit id unknown hash
2D graphics backend Skia
Command Line Args
--ppapi-flash-path=/nix/store/ln5sj7v6ynxf1vs50y707jj3bh21rbif-chromium-binary-plugins-flash/lib/libpepflashplayer.so
--ppapi-flash-version=15.0.0.239 --flag-switches-begin --ignore-gpu-blacklist
--flag-switches-end
Driver Information
Initialization time 237
Sandboxed true
GPU0 VENDOR = 0x0000, DEVICE= 0x0000
Optimus false
AMD switchable false
Driver vendor Mesa
Driver version 10.2.9
Driver date
Pixel shader version 1.30
Vertex shader version 1.30
Machine model name
Machine model version
GL_VENDOR Intel Open Source Technology Center
GL_RENDERER Mesa DRI Intel(R) Sandybridge Mobile
GL_VERSION 3.0 Mesa 10.2.9
...
indow system binding vendor SGI
Window system binding version 1.4
Window system binding extensions GLX_ARB_create_context
GLX_ARB_create_context_profile GLX_ARB_create_context_robustness
GLX_ARB_fbconfig_float GLX_ARB_framebuffer_sRGB GLX_ARB_multisample
GLX_EXT_create_context_es2_profile GLX_EXT_framebuffer_sRGB
GLX_EXT_import_context GLX_EXT_texture_from_pixmap GLX_EXT_visual_info
GLX_EXT_visual_rating GLX_MESA_copy_sub_buffer GLX_OML_swap_method
GLX_SGI_swap_control GLX_SGIS_multisample GLX_SGIX_fbconfig GLX_SGIX_pbuffer
GLX_SGIX_visual_select_group GLX_INTEL_swap_event
Window manager Xfwm4
Compositing manager No
Direct rendering Yes
Reset notification strategy 0x8252
GPU process crash count 0
Log Messages
[3040:3040:1209/171937:ERROR:gpu_video_decode_accelerator.cc(301)] : Not
implemented reached in void
content::GpuVideoDecodeAccelerator::Initialize(media::VideoCodecProfile,
IPC::Message*)HW video decode acceleration not available.
[3040:3040:1209/171937:ERROR:gpu_video_decode_accelerator.cc(301)] : Not
implemented reached in void
content::GpuVideoDecodeAccelerator::Initialize(media::VideoCodecProfile,
IPC::Message*)HW video decode acceleration not available.
I have attached the contents of /sys/class/drm/card1/error.
I have also filed an issue at https://github.com/NixOS/nixpkgs/issues/5272 but
I was told to file an issue here.
--
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/20141209/9611d156/attachment.html>
More information about the intel-gfx-bugs
mailing list