<div class="gmail_quote">2012/2/23 Mathias Fröhlich <<a href="mailto:Mathias.Froehlich@gmx.net">Mathias.Froehlich@gmx.net</a>> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Christian, <div class="im"> On Thursday, February 23, 2012 15:18:42 Christian König wrote: > The function radeon_bo_list_validate can cause a > bo to move, resulting in a different sync_obj > and a dependency to wait for this move to finish. > > Signed-off-by: Christian König <<a href="mailto:deathsimple@vodafone.de">deathsimple@vodafone.de</a>> > Reviewed-by: Alex Deucher <<a href="mailto:alexander.deucher@amd.com">alexander.deucher@amd.com</a>> </div>I am not sure, but to me this looks like this could fix these kind of gpu lockups that I experience since some time every now and then. The usual symptom is that I get the radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec GPU lockup (waiting for 0x00682AC3 last fence id 0x00682AC2) [...] kernel message. Each time with the fence being off by one like in the example above. If this change has the potential to fix this issue I think this particular patch should be considered for the current upstream kernel release. Mathias </blockquote></div> No this patch doesn't. This patch is all about getting proper sync btw different rings. Sorry for the deception. Cheers, Jerome