Am 19.11.2014 um 14:16 schrieb Kai Wasserbäch: > Dear Christian, > Christian König wrote on 19.11.2014 14:01: >> From: Christian König <christian.koenig at amd.com> >> >> This way the necessary VM update is kicked off immediately >> if all BOs involved are in GPU accessible memory. >> >> v2: fix vm lock >> v3: immediately update unmaps as well >> >> Signed-off-by: Christian König <christian.koenig at amd.com> >> --- >> drivers/gpu/drm/radeon/radeon_gem.c | 64 >> +++++++++++++++++++++++++++++++++++++ >> 1 file changed, 64 insertions(+) > Is this a fix for <http://thread.gmane.org/gmane.comp.video.dri.devel/118415> > which I bisected to the v2 of this patch > (<http://thread.gmane.org/gmane.comp.video.dri.devel/118415/focus=118425>) as > present on the drm-next-3.19-wip branch?
Yes and no, it was actually the patch before this one which triggered the problem. The last one just made it much more likely to appear. Please test the whole patchset on top of Dave's drm-next tree if your problem still exists. Thanks, Christian. > > Cheers, > Kai >
