<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - SIGBUS in EVERGREENUploadToScreen after hibernation (Linux 3.12.4-tuxonice)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72716#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - SIGBUS in EVERGREENUploadToScreen after hibernation (Linux 3.12.4-tuxonice)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72716">bug 72716</a>
from <span class="vcard"><a class="email" href="mailto:txtoxtox285@googlemail.com" title="txtoxtox285@googlemail.com">txtoxtox285@googlemail.com</a>
</span></b>
<pre>During the many cycles of “printk, compile, reboot, suspend, resume, crash X”
I’ve found that the problem may have to do with the fact that I load radeon.ko
during my initramfs before attempting resume by echoing into /sys/power/resume
or /sys/power/tuxonice/do_resume.
If I do *not* load radeon.ko into the “booting” kernel (i.e., the one which is
then replaced by the “resuming” kernel), I couldn’t reproduce the crash.
Furthermore, I do *not* get these four messages from the “resuming” kernel
about a lockup:
[ 864.574325] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[ 864.574328] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000004
last fence id 0x0000000000000002)
[ 864.574331] [drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait failed (-35).
[ 864.574334] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
ring 5 (-35).</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>