Bug 102310 - GPU HANG: ecode 4:2:0x00000000, reason: Hang on bsd ring, action: reset
Summary: GPU HANG: ecode 4:2:0x00000000, reason: Hang on bsd ring, action: reset
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-19 21:06 UTC by michel.munnix
Modified: 2017-08-25 18:00 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (62.44 KB, text/plain)
2017-08-19 21:06 UTC, michel.munnix
no flags Details
/sys/class/drm/card0/error (850.19 KB, text/plain)
2017-08-19 21:07 UTC, michel.munnix
no flags Details
dmesg with "drm.debug=0x1e log_buf_len=1M" (106.68 KB, text/plain)
2017-08-19 21:32 UTC, michel.munnix
no flags Details
/sys/class/drm/card0/error when started with debug flags (702.77 KB, text/plain)
2017-08-19 21:33 UTC, michel.munnix
no flags Details

Description michel.munnix 2017-08-19 21:06:24 UTC
Created attachment 133631 [details]
dmesg

kernel: 4.4.79-19-default
distribution: opensuse 42.3
reproducible: every time
when starting graphics session as normal user as well as root user
no mouse pointer, keyboard unresponsive

error in dmesg
Comment 1 michel.munnix 2017-08-19 21:07:49 UTC
Created attachment 133632 [details]
/sys/class/drm/card0/error
Comment 2 michel.munnix 2017-08-19 21:32:13 UTC
Created attachment 133633 [details]
dmesg with "drm.debug=0x1e log_buf_len=1M"

with debug flags, screen, mouse and keyboard are usable
temporary artefacts during session setup
after that, cursor is in top left corner of a black square moving with the cursor
Comment 3 michel.munnix 2017-08-19 21:33:10 UTC
Created attachment 133634 [details]
/sys/class/drm/card0/error when started with debug flags
Comment 4 Chris Wilson 2017-08-21 11:41:59 UTC
Good new, bad news. It was fixed circa v4.6 or v4.9 with the request/context overhaul, but I can't remember the precise fix anymore.


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.