https://bugzilla.kernel.org/show_bug.cgi?id=85421 --- Comment #18 from Hin-Tak Leung <htl10@xxxxxxxxxxxxxxxxxxxxx> --- (In reply to Alex Deucher from comment #14) > Please make sure your version of mesa has this patch: > http://cgit.freedesktop.org/mesa/mesa/commit/ > ?id=ae4536b4f71cbe76230ea7edc7eb4d6041e651b4 This seems no good /insufficient. I just had a lock-up with 10.3.5, which includes it. With kernel 3.17.6-200.fc20.x86_64, if that means anything. Also it looks like I upgraded firefox to v34 (from v33) 5 days ago. I was merely opening a few more tabs on firefox when it happened. Though 20 minutes before then my computer came out of a suspend, and before the suspend, I was using kvm and virtualbox a bit. Switching VT was still possible so I was able to reboot cleanly. The failure message seems slightly different, so just in case it means anything, ... [71241.232157] radeon 0000:00:01.0: ring 0 stalled for more than 10002msec [71241.232173] radeon 0000:00:01.0: GPU lockup (waiting for 0x000000000052e910 last fence id 0x00 0000000052e90d on ring 0) [71241.232337] radeon 0000:00:01.0: failed to get a new IB (-35) [71241.232347] [drm:radeon_cs_ib_fill] *ERROR* Failed to get ib ! [71241.279772] radeon 0000:00:01.0: Saved 15657 dwords of commands on ring 0. ... [71252.356774] [drm:cik_ring_test] *ERROR* radeon: ring 1 test failed (scratch(0x3010C)=0xCAFEDEA D) [71252.718837] [drm:cik_ring_test] *ERROR* radeon: ring 2 test failed (scratch(0x3010C)=0xCAFEDEA D) [71252.836977] [drm:cik_sdma_ring_test] *ERROR* radeon: ring 3 test failed (0xCAFEDEAD) [71252.836992] [drm:cik_resume] *ERROR* cik startup failed on resume [71252.837260] [drm] ib test on ring 0 succeeded in 0 usecs [71252.837790] [drm] ib test on ring 6 succeeded [71252.838167] [drm] ib test on ring 7 succeeded [71254.210168] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed [71254.210182] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed [71257.654395] radeon 0000:00:01.0: still active bo inside vm [71257.765448] radeon 0000:00:01.0: still active bo inside vm [71258.526881] radeon 0000:00:01.0: still active bo inside vm [71265.473102] radeon 0000:00:01.0: couldn't schedule ib ... I cam supply the dmesg if needed. Seeing as the patch does not work/insufficient, and my best experience so far is 10.2.9 (lasted 3 weeks, without the patch), my worst experience is 10.3.3 (less than a day), and 10.3.4/10.3.5 (patch included) lasted a week, I am going back to 10.2.9, and adding the patch to it. If the patch improves 10.2.9 the way it did from 10.3.3 -> 10.3.4/10.3.5, i.e. make 10.2.9 lasts a few months, I'd be happy enough. -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
