Bug 104623 - [drm] GPU HANG: ecode 6:0:0x00d1bba2, in Xorg [1837], reason: Hang on render ring, action: reset
Summary: [drm] GPU HANG: ecode 6:0:0x00d1bba2, in Xorg [1837], reason: Hang on render ...
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/modesetting (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-14 14:54 UTC by Martin Koller
Modified: 2018-12-13 18:12 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
dump file (141.72 KB, application/gzip)
2018-01-14 14:54 UTC, Martin Koller 		no flags Details
Xorg.0.log (30.74 KB, text/x-log)
2018-01-14 14:54 UTC, Martin Koller 		no flags Details
View All

Description Martin Koller 2018-01-14 14:54:15 UTC 
Created attachment 136715 [details]
dump file

I upgraded to openSuse leaf 42.3 on an acer aspire one Laptop,
and very often I now get GPU hangs where dmesg says

drm/i915: Resetting chip after gpu hang

checking dmesg I also found the following which led me to create this report:

[  442.799709] [drm] GPU HANG: ecode 6:0:0x00d1bba2, in Xorg [1837], reason: Hang on render ring, action: reset
[  442.799713] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[  442.799714] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[  442.799715] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  442.799716] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[  442.799717] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  442.799781] drm/i915: Resetting chip after gpu hang
Comment 1 Martin Koller 2018-01-14 14:54:36 UTC 
Created attachment 136716 [details]
Xorg.0.log
Comment 2 GitLab Migration User 2018-12-13 18:12:46 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/xorg/xserver/issues/69.

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.