Created attachment 894972 [details] journalctl output 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). Attaching the journalctl output from the time of resuming from sleep, which indicates that the radeon driver is freaking out about UVD, among other things: > [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).
Created attachment 894974 [details] screenshot of a kernel panic Also, this might be unrelated, but I got this kernel panic during a yum update before I restarted. Not sure if that's the driver blowing up randomly or if it was triggered by yum (this wouldn't be the first time I see that, I think).
I have the same problem on my 3 (three!!!) days old computer: After shrinking the Win8 partition and doing a dual-boot install, I did not get the error - until I did a yum -y update. Here are the relevant logs and other info. [root@samwise ~]# dmesg|grep UVD [ 5.826503] [drm] UVD initialized successfully. [ 24.773442] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 25.794543] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 26.815624] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 27.836724] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 28.857800] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 29.878874] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 30.899947] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 31.921049] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 32.942122] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 33.963195] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 33.983238] [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!! [ 33.983262] [drm:si_startup] *ERROR* radeon: failed initializing UVD (-1). [root@samwise ~]# lspci -k|grep -A3 VGA 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) Subsystem: Dell Device 05ee Kernel driver in use: i915 Kernel modules: i915 -- 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M] (rev ff) Kernel driver in use: radeon Kernel modules: radeon There is a similar|same bug being investigated over at https://bugzilla.kernel.org/show_bug.cgi?id=71891 so maybe the solution, or at least a workaround is close.
This occurs on power up with my system and is accompnied by long delays in the boot process. The system eventually comes up but compositing functions in the Enlightenment 18 desktop do not work and must be disabled. There are long delays during power down and the same sequence of error messages appear. Everything is fine if I boot the 3.13.10-200 kernel so this more likely the "radeon" module rather than the X11 driver.
Moving to component "kernel" (Linux) instead of x11-xorg-drv-amd, but not sure if that's the right component (or how to get the right people to look at this)…
Today I installed the 3.14.5-200.fc20.x86_64 kernel and my original one (from when installing) got lost. But, before that, booting into [root@samwise ~]# yum history info 1|grep kernel Install kernel-3.11.10-301.fc20.x86_64 @koji-override-0/$releasever Install kernel-modules-extra-3.11.10-301.fc20.x86_64 actually did not cause any problems.
Also filed a copy of this bug report upstream in the Xorg project, to see if they have anything to say about it: https://bugs.freedesktop.org/show_bug.cgi?id=80066
It generally seems to be working with the 3.14.7-200 kernel (64-bit) although I have not verified detailed functionality.
Interesting. I am indeed seeing normal performance on resume with the 3.14.7 kernel now (tried suspending and resuming two times, we'll see if things stay stable). I'm not seeing UVD error messages in "journalctl -f" so far. Perhaps Knut can confirm. See also https://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.14.7 (search for Radeon) if you want to check and figure out which commit may have actually solved this...
Yep! This works just fine now. thanks!
Thanks.