(In reply to AmarildoJr from comment #27)
> (In reply to Marek Ol=C5=A1=C3=A1k from comment #26)
> > (In reply to AmarildoJr from comment #25)
> > > Marek, since you work for AMD, I wonder if you could get a f=
ew hints for the
> > > fix on Catalyst's sources?
> >=20
> > It's not so simple. This is a bug somewhere in the Mesa driver su=
ch that
> > looking at other drivers won't likely help.
>=20
> This is a very weird issue. I think it may not be in Mesa, and here's =
why:
>=20
> * 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, t=
he
> 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 ve=
rsion
> 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 to=
day
> since I'm testing a few drivers in Linux;
> * On vanilla Arch with Catalyst/FGLRX, the problem doesn't happen;
>=20
> So I do think this issue is much bigger than everybody thinks and only
> happens with a certain combination of Mesa, Kernel, Firmware, and poss=
ibly
> libdrm, llvm, and other pieces of software as well.
>=20
> What I really think is that VALVe should investigate this since this p=
roblem
> 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?