Re: [bisected] drm/radeon: fences regression

[Christian König]

Hi Ortwin,

unfortunately the iMacs are notorious problematic and it's likely that 
something didn't worked before and you never noticed it because the 
kernel didn't complained. Have you ever tried to use UVD on that system?

On the other hand the failed UVD init shouldn't affect the rest of the 
system (3D should work fine), so there is really something odd here.

Please open up a bug report on 
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI component 
DRM/Radeon and attach at least the full dmesg output of 3.13 as well as 
3.12.

Thanks in advance,
Christian.

Am 22.03.2014 16:16, schrieb Ortwin Glück:
> Hi,
>
> I am seeing a GPU lockup from any v3.13 up to 3.14-rc7, which 
> basically renders my computer unusable under recent kernels :-(
>
> [   55.762710] radeon 0000:01:00.0: GPU lockup CP stall for more than 
> 10000msec
> [   55.762715] radeon 0000:01:00.0: GPU lockup (waiting for 
> 0x0000000000000004 last fence id 0x000000000000000 on ring 5)
> [   55.762717] [drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait 
> failed (-35).
> [   55.762720] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed 
> testing IB on ring 5 (-35).
>
> Hardware is an iMac 11,2 with a Radeon 4670 M96XT (RV730), 256MB GDDR3.
>
>
> Bisected to this commit:
>
> commit f9eaf9ae782d6480f179850e27e6f4911ac10227
> Author: Christian König <christian.koenig@xxxxxxx>
> Date:   Tue Oct 29 20:14:47 2013 +0100
>
>     drm/radeon: rework and fix reset detection v2
>
>     Stop fiddling with jiffies, always wait for 
> RADEON_FENCE_JIFFIES_TIMEOUT.
>     Consolidate the two wait sequence implementations into just one 
> function.
>     Activate all waiters and remember if the reset was already done 
> instead of
>     trying to reset from only one thread.
>
>     v2: clear reset flag earlier to avoid timeout in IB test
>
> Unfortunately this patch no longer cleanly unapplies on v3.13.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/