Bug 75900

Created attachment 95322 [details]
Serious Sam 3 log when segfault

With R600_DEBUG=nosb, Left 4 Dead 2 crash even faster (5 seconds after the scenery is loaded).

With R600_DEBUG=hyperz I can play L4D2 several minutes before a GPU lockup.

I reverted the commit. Does it help?

Yes current master works correctly now.

I'm experiencing the same problems on my HD6850, currently upgrading to master to see if it helps, however unlike Benjamin case my card hanged when I watched some movie (vpdu backend), the other time I was viewing some web page - there was a (old, via wine) game running in the backround though. 

The crashes seemed completely random, no indication what might have caused it. I'll attach log file containing first hang (I had to do a hard reset, sysrq didn't work, on the second occasion sysrq did work but there was no info in the log file but I think I've waited long enough, strange).

Created attachment 95360 [details]
Log including first crash

(In reply to comment #6)
> I'm experiencing the same problems on my HD6850, currently upgrading to
> master to see if it helps, however unlike Benjamin case my card hanged when
> I watched some movie (vpdu backend), the other time I was viewing some web
> page - there was a (old, via wine) game running in the backround though. 
> 
> The crashes seemed completely random, no indication what might have caused
> it. I'll attach log file containing first hang (I had to do a hard reset,
> sysrq didn't work, on the second occasion sysrq did work but there was no
> info in the log file but I think I've waited long enough, strange).

Please let me know after you test Mesa master. Thanks.

I am experiencing some issues with Diablo III via wine after these changes (I believe) as well. Upon loading the GPU to any extent, random large polygons cover large portions of the screen. Not super pretty. Reverting to a mesa build from the 5th fixed things, but the most recent update to master did *not*.

I backtraced and found f112ba03bbd6072df9f8879bb231f7f0abb14d2e to be my first bad commit. Not sure if this should be a separate bug report or if that is causing issues for anyone else.

Created attachment 95374 [details]
dmesg log showing GPU lockups

My RV790 had also started locking up while playing WoW, but is now magically fixed.

cf1c52575d6fea966d818eac4a32ec2decc48576    GOOD
a995f564c7b226438d10e5d5895692ed1fd550e3    BAD	
1e25aa4cdb3bb1f190ea3905eb1d169e0c5a1ef0    GOOD

I have attached the dmesg log from the lockups, in case they might be useful.

FYI, Marek's latest patches on the ML fixed my issue listed above.

(In reply to comment #12)
> FYI, Marek's latest patches on the ML fixed my issue listed above.

This is probably not the same bug than mine indeed.

(In reply to comment #8)
> (In reply to comment #6)
> > I'm experiencing the same problems on my HD6850, currently upgrading to
> > master to see if it helps, however unlike Benjamin case my card hanged when
> > I watched some movie (vpdu backend), the other time I was viewing some web
> > page - there was a (old, via wine) game running in the backround though. 
> > 
> > The crashes seemed completely random, no indication what might have caused
> > it. I'll attach log file containing first hang (I had to do a hard reset,
> > sysrq didn't work, on the second occasion sysrq did work but there was no
> > info in the log file but I think I've waited long enough, strange).
> 
> Please let me know after you test Mesa master. Thanks.

With current master I'm no longer experiencing any hangs, I can't however guarantee it's the same problem, because I've no idea how to reproduce it. 

All I know is that the problem was introduced somewhere between 4-7.03, I guess I could cherry pick or "revert the revert" and see what happens but if I'm going to do that I might as well collect some additional information, just let me know what you're interesed in.

(In reply to comment #14)
> With current master I'm no longer experiencing any hangs, I can't however
> guarantee it's the same problem, because I've no idea how to reproduce it. 
> 
> All I know is that the problem was introduced somewhere between 4-7.03, I
> guess I could cherry pick or "revert the revert" and see what happens but if
> I'm going to do that I might as well collect some additional information,
> just let me know what you're interesed in.

I just wanted to know if you were still seeing any hangs, and you weren't, which is great.

This has been fixed. Closing.