![]() So I do think this issue is much bigger than everybody thinks and only happens with a certain combination of Mesa, Kernel, Firmware, and possibly libdrm, llvm, and other pieces of software as well. * On vanilla Arch with Catalyst/FGLRX, the problem doesn't happen * I'm not 100% sure I downgraded the Firmware on Arch, but I'll try today since I'm testing a few drivers in Linux * On the same Arch Linux with Mesa and Kernel downgraded (Kernel to version 3.16 and even 3.10), the problem still happens * On Arch Linux with Mesa downgraded to 10.3, the problem happens * On the same Debian with Mesa backported and the Kernel backported, the problem still doesn't happen * On the same Debian, but with mesa backported, the problem also doesn't happen * On Debian Jessie with kernel 3.16 and Mesa 10.3, the problem doesn't happen ![]() I think it may not be in Mesa, and here's why: > looking at other drivers won't likely help. This is a bug somewhere in the Mesa driver such that > Marek, since you work for AMD, I wonder if you could get a few hints for the > (In reply to AmarildoJr from comment #25) (In reply to Marek Olšák from comment #26) Package update history that lead to a change in behaviour Stellaris run via steam: GALLIUM_DDEBUG="pipelined 2000" %command% Second patch to fix system lockup after gpu reset This helps avoid a complete crash when a lockup occurs. ![]() Kernel dmesg around the time of the lockup.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |