<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Random radeonsi crashes"
href="https://bugs.freedesktop.org/show_bug.cgi?id=79980#c61">Comment # 61</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Random radeonsi crashes"
href="https://bugs.freedesktop.org/show_bug.cgi?id=79980">bug 79980</a>
from <span class="vcard"><a class="email" href="mailto:jackdachef@gmail.com" title="jackdachef@gmail.com">jackdachef@gmail.com</a>
</span></b>
<pre>thanks for all the fixes !
currently using
<a href="http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.17-rebased-on-fixes">http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.17-rebased-on-fixes</a>
and it looks pretty stable so far (radeonsi, R9 270X)
even with 3.14.14 there were some (pretty seldom) but occasional crashes of X:
vanilla 3.16-rc6 was pretty much unusable (X + box hardlocks)
and especially <a href="http://cgit.freedesktop.org/~agd5f/linux/?h=drm-next-3.17-wip">http://cgit.freedesktop.org/~agd5f/linux/?h=drm-next-3.17-wip</a>
(*without* the fixes) had dozens of gpu crashes yesterday evening/night which
were recovering (probably thanks to radeon.hard_reset=1) without crashing X and
hardlocking the system:
ring 0 stalled for more than 10010msec GPU lockup
waiting for ... last fence id ... on ring 0
GPU softreset ...
[drm] UVD initialized successfully.
[drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35).
[drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35)
radeon 0000:01:00.0: ib ring test failed (-35)
couldn't schedule ib
still active bo inside vm
GPU softreset ...
radeon 0000:01:00.0: ring 5 stalled for more than 10000msec
radeon 0000:01:00.0: GPU lockup (waiting for ... last fence id ... on ring 5
[drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait failed
(-35).[drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5
(-35)[drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed)
radeon 0000:01:00.0: ring 5 stalled for more than 3438516msec
radeon 0000:01:00.0: GPU lockup (waiting for ... last fence id ... on ring 5)
radeon 0000:01:00.0: ffff8807cfa63000 pin failed
[drm:radeon_crtc_page_flip] *ERROR* failed to pin new rbo buffer before flip
and messages in Xorg.0.log with
(WW) RADEON(0): radeon_dri2_flip_event_handler: Pageflip completion event has
impossible msc 89175 < target_msc 89176
and
(WW) RADEON(0): flip queue failed: Invalid argument
(WW) RADEON(0): Page flip failed: Invalid argument
currently still running with radeon.hard_reset=1 - but that probably shouldn't
be needed anymore
best trigger for those occasional crashes was using chromium/chrome, watching
videos on youtube, switching apps via alt+tab (using an composited desktop with
compiz-fusion 0.8.8) and from time to time opening up gmail (which, if I
remember correctly would cause the gpu to crash at least twice of these
countless times yesterday)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>