linux-kernel - drm/radeon bisected 3.13 regression: GPU lockup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Tue, 21 Jan 2014 23:43:17 +0100
From:	Ortwin Glück <odi@....ch>
To:	linux-kernel@...r.kernel.org, christian.koenig@....com,
	alexander.deucher@....com
Subject: drm/radeon bisected 3.13 regression: GPU lockup

Hi,

I am seeing a GPU lockup since v3.13:

[   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@....com>
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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/