(In reply to russianneuromancer from comment #13)
> Michel, Maarten, seems like issue that I reported originally is not same
> issue that polo reporting. For me DRI3 usage cause kernel module crash, for
> him using DRI3 instead of DRI2 is kind of workaround. 
> What you think?

It's probably better if polo files his/her own upstream report then, or sticks
to the downstream one. Since that problem seems to be a regression, it should
be possible to isolate it with git bisect.

(In reply to Maarten Lankhorst from comment #11)
> If this causes a GPF in ttm_bo_wait my guess is radeon has a fence
> refcounting bug, [...]

Indeed, that happened in https://bugs.freedesktop.org/show_bug.cgi?id=93017#c5
. Christian, any ideas where our fence reference counting might be wrong?