Bug 106421 - [gm45] Stray GPU writes
Summary: [gm45] Stray GPU writes
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
Depends on:
Reported: 2018-05-06 16:05 UTC by pistenflitzer
Modified: 2019-09-25 19:11 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

/sys/class/drm/card0/error (40.40 KB, text/plain)
2018-05-06 16:05 UTC, pistenflitzer

Description pistenflitzer 2018-05-06 16:05:55 UTC
Created attachment 139395 [details]

I just started "git gui", when the notebook froze for a few seconds. Afterwards, I could access most running applications, but chrome only rendered the tab bar, and plasmashell would not start again.

I had only just updated the KDE libraries from 5.44.0 to 5.45.0 when this happened. Not sure if this is related.

from dmesg:
[ 6202.821326] [drm] GPU HANG: ecode 4:0:0xefdcfff7, in chrome [2583], reason: Hang on rcs0, action: reset
[ 6202.821327] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 6202.821328] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 6202.821329] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 6202.821329] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 6202.821330] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 6202.821370] i915 0000:00:02.0: Resetting chip after gpu hang
[ 6207.968047] i915 0000:00:02.0: i915_reset_device timed out, cancelling all in-flight rendering.
[ 6212.288101] i915 0000:00:02.0: Failed to reset chip
Comment 1 Denis 2018-05-07 15:58:55 UTC
Hello. Could you please provide more information about your software?
glxinfo -B with mesa version would be great. Right now there are about 5 tickets about GPU hangs in kde plasmashell on different distributives, so maybe it is one issue...
Comment 2 pistenflitzer 2018-05-07 16:17:12 UTC
Please let me know if you need more information.

$ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Mobile Intel® GM45 Express Chipset  (0x2a42)
    Version: 18.0.2
    Accelerated: yes
    Video memory: 1536MB
    Unified memory: yes
    Preferred profile: compat (0x2)
    Max core profile version: 0.0
    Max compat profile version: 2.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 2.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset
OpenGL version string: 2.1 Mesa 18.0.2
OpenGL shading language version string: 1.20

OpenGL ES profile version string: OpenGL ES 2.0 Mesa 18.0.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
Comment 3 GitLab Migration User 2019-09-25 19:11:02 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1721.

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.