Comment # 28
on bug 93649
from Vedran Miletić
(In reply to AmarildoJr from comment #27) > (In reply to Marek Olšák from comment #26) > > (In reply to AmarildoJr from comment #25) > > > Marek, since you work for AMD, I wonder if you could get a few hints for the > > > fix on Catalyst's sources? > > > > It's not so simple. This is a bug somewhere in the Mesa driver such that > > looking at other drivers won't likely help. > > This is a very weird issue. I think it may not be in Mesa, and here's why: > > * On Debian Jessie with kernel 3.16 and Mesa 10.3, the problem doesn't > happen; > * On the same Debian, but with mesa backported, the problem also doesn't > happen; > * On the same Debian with Mesa backported and the Kernel backported, the > problem still doesn't happen; > * On Arch Linux with Mesa downgraded to 10.3, the problem happens; > * On the same Arch Linux with Mesa and Kernel downgraded (Kernel to version > 3.16 and even 3.10), the problem still happens; > * 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 vanilla Arch with Catalyst/FGLRX, the problem doesn't happen; > > 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. > > What I really think is that VALVe should investigate this since this problem > started happening after they introduced mandatory Texture Streaming. Is the elephant in the room in this case the LLVM version difference between the two setups?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
