Comment # 3 on bug 60347 from
(In reply to comment #2)
> 
> I've narrowed it down to one of these two kernel patches:
> 
> 4ac0533abaec2b83a7f2c675010eedd55664bc26
> cf4ccd016bae1a03bb38170eb54b5db4b04e0545

It's probably a mesa bug then.  Since those two patches just enable mesa to use
additional features (htile and DMA).  Probably one of these mesa commits:
24b1206ab2dcd506aaac3ef656aebc8bc20cd27a
6532eb17baff6e61b427f29e076883f8941ae664
325422c49449acdd8df1eb2ca8ed81f7696c38cc

Does setting the env var R600_HYPERZ=0 or resetting your git tree back to
cf5632094ba0c19d570ea47025cf6da75ef8457a fix the issue?


You are receiving this mail because: