[vulkan] GPU HANG: ecode 7:0:0x86f2fdfd, reason: Hang on render ring, action: reset
Submitted by git..@..ace.de
Assigned to Intel 3D Bugs Mailing List
Link to original bug (#100518)
Description
This error occoured to me while playing around with Vulkan.
kernel: [drm] GPU HANG: ecode 7:0:0x86f2fdfd, in triangle [30010], reason: Hang on render ring, action: reset kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. kernel: [drm] Please file a new bug report on bugs.freedesktop.org against DRI -> DRM/Intel kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error kernel: drm/i915: Resetting chip after gpu hang kernel: drm/i915: Resetting chip after gpu hang
After starting my program (triangle), my Xorg hung for several seconds, then crashed. I saw the above message in my dmesg. Error behaviour differs slightly, sometimes Xorg crashes, most of the time it hangs completely and I have to reboot.
The bug is reproducible under the following conditions:
- create device memory allocation with size=1MiB
- create a depth-stencil image with dimensions 800x600 and format VK_FORMAT_D32_SFLOAT_S8_UINT
- bind the memory allocation (which is obviously too small!) to the DS image
- draw something and watch it failing
If you really need it, I can attach the crashdump but I would like to avoid this since I'm not sure whether there is some sensitive data inside the render ring dump.
The error code sometimes seems to be 7:0:0x85ffffff, but unfortunately I haven't been able to get a crashdump for this error code, because the machine locked up and I had to reboot.
CPU is a Core i5-3210M.