Bug 106242

Summary: [snb] GPU HANG: ecode 6:0:0xf388fff8, in blockGen (VTK)
Product: Mesa Reporter: bandfrosch
Component: Drivers/DRI/i965Assignee: Intel 3D Bugs Mailing List <intel-3d-bugs>
Status: RESOLVED MOVED QA Contact: Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity: minor    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
i915 platform: i915 features:
Attachments: bzipped /sys/class/drm/card0/error gpu crash dump

Description bandfrosch 2018-04-25 19:18:23 UTC
Created attachment 139110 [details]
bzipped /sys/class/drm/card0/error gpu crash dump

OS : almost up-to-date openSUSE tumbleweed ( 24th of april 2018)
uname -a: Linux wladimir 4.16.1-1-default #1 SMP PREEMPT Mon Apr 9 06:27:59 UTC 2018 (fc6541a) x86_64 x86_64 x86_64 GNU/Linux

Mesa Version : 18.0.0-193.1

system hangs for 5 seconds while working with homegrown VTK ( OpenGL ) application

[ 3191.906548] [drm] GPU HANG: ecode 6:0:0xf388fff8, in blockGen [7146], reason: Hang on rcs0, action: reset
[ 3191.906551] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 3191.906552] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 3191.906552] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 3191.906553] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 3191.906555] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 3191.906606] i915 0000:00:02.0: Resetting chip after gpu hang
[ 3195.964336] asynchronous wait on fence i915:[global]:161ee timed out
[ 3200.892410] i915 0000:00:02.0: Resetting chip after gpu hang
[ 3209.916414] i915 0000:00:02.0: Resetting chip after gpu hang

Comment 1 GitLab Migration User 2019-09-25 19:10:59 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/1720.

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.