<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - With kernel 3.14, terrible radeonsi performance with a RadeonHD 7770 resuming from suspend/sleep - "*ERROR* UVD not responding, trying to reset the VCPU!!!""
href="https://bugs.freedesktop.org/show_bug.cgi?id=80066">80066</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>xorg-driver-ati@lists.x.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>With kernel 3.14, terrible radeonsi performance with a RadeonHD 7770 resuming from suspend/sleep - "*ERROR* UVD not responding, trying to reset the VCPU!!!"
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>xorg-team@lists.x.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>nekohayo@gmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>Driver/Radeon
</td>
</tr>
<tr>
<th>Product</th>
<td>xorg
</td>
</tr></table>
<p>
<div>
<pre>Initially filed downstream on Fedora 20:
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1097045">https://bugzilla.redhat.com/show_bug.cgi?id=1097045</a>
See that bug report for details, systemd journal logs, etc.
journalctl output: <a href="https://bugzilla.redhat.com/attachment.cgi?id=894972">https://bugzilla.redhat.com/attachment.cgi?id=894972</a>
Since kernel 3.14 on Fedora 20, I can't suspend my desktop computer anymore.
The suspend/resume operation "seems to work" generally speaking, but it borks
the state of the graphics driver. This used to work fine in kernel 3.12 (and I
think 3.13 too).
Symptoms: extremely sluggish operations for anything that involves 3D (ex:
gnome shell animations). This persists until a complete reboot (reloading gnome
shell, or using "systemctl isolate multi-user.target && systemctl isolate
graphical.target" doesn't solve it).
The journalctl output seems to indicate that the radeon driver is freaking out
about UVD, among other things:
<span class="quote">> [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
> [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!!
> [drm:si_startup] *ERROR* radeon: failed initializing UVD (-1).</span ></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>