| Bug ID | 107204 |
|---|---|
| Summary | GPU hang (ring gfx timeout) in OpenGL game |
| Product | Mesa |
| Version | git |
| Hardware | All |
| OS | All |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | fbz-me@milek7.pl |
| QA Contact | dri-devel@lists.freedesktop.org |
Created attachment 140= 587 [details] Dumps from GALLIUM_DDEBUG It hangs in OpenGL game immediately after startup almost always (but someti= mes it goes through and works) with dmesg message: >[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring g= fx timeout, last signaled seq=3D3324, last emitted seq=3D3327 I tested it on Radeon RX580, mainline kernel 4.18, Mesa 18.1.3 and Mesa git c0874947f1. I could provide game code for testing but I would have to package minimal assets as full game weights pretty much.
| What | Removed | Added |
|---|---|---|
| Summary | GPU hang (ring gfx timeout) in OpenGL game | GPU hang (ring gfx timeout) with out of bounds UBO read in s= hader |
It turned out that the cause was uninitialized UBO, which depe= nding on memory contents leaded to out of bounds UBO array read in fragment shader. It probably shouldn't bring down whole GPU, though.
| What | Removed | Added |
|---|---|---|
| Resolution | --- | MOVED |
| Status | NEW | RESOLVED |
-- 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/1320.