Page MenuHome

Blender 2.8 triggers GPU lockup when entering Edit Mode
Open, Needs TriagePublic

Description

System Information
Operating system: Linux openSUSE Tumbleweed x64
Driver: Kernel 4.19.11, Mesa 18.3.1, amdgpu module
Graphics card: Radeon R9 390 (GCN 2.0)

Blender Version
Broken: 2.80 7c438e5366b2
Worked: 2.79b, 2.8 (roughly 2 week old build)

Short description of error
When entering Edit Mode on an object, a GPU lockup occurs almost immediately, requiring a hardware restart. This seems to happen for objects with a high enough amount of vertices (no problem with the default cube). The image freezes, mouse cursor cannot be moved, NumLock / CapsLock keyboard leds can't be toggled. The HDD led does not flash meaning the hard drive isn't busy.

Exact steps for others to reproduce the error
Download the latest development version of Blender 2.8 from the https://builder.blender.org/download page, ideally the version linked above granted the link remains available. Delete the default cube, press Shift + A to add a new object, then add an UV sphere. Upon doing this you should see a popup in the lower-left corner of the screen; Set the Segments to 128 and the Rings to 64. Now press Tab to go into Edit Mode with the sphere selected.

Result
You should begin to see graphical corruption on the screen. In my case I see lines stretching from each vertice to the edge of the screen. Within a few seconds if not instantly, the entire system will freeze up.

Details

Type
Bug

Event Timeline

A screenshot of the graphical corruption which can be observed moments before the crash.

this situation had been improved about a month ago .. with the last (now) mesa 19 - devel ..
but now changes have been made and shadow ESM and VSM and Lights no longer work ...
follow this bug report .. for detailed information ..
let's see if we solve this problem

https://developer.blender.org/T60001

In the meantime I've preformed a test which was recommended to me by another user. The crash seems to be unaffected by booting with either "amdgpu.dc=0" or "amdgpu.dc=1" and will occur identically in both cases.