You are not logged in.
Whenever I start my system, or resume from suspend or even shutdown, systemd shows these errors:
Apr 13 17:40:08 Ishaan-PC kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Apr 13 17:40:08 Ishaan-PC kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Apr 13 17:40:08 Ishaan-PC kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Apr 13 17:40:08 Ishaan-PC kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Apr 13 17:40:08 Ishaan-PC kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Apr 13 17:40:08 Ishaan-PC kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Apr 13 17:40:08 Ishaan-PC kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Apr 13 17:40:08 Ishaan-PC kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Apr 13 17:40:08 Ishaan-PC kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Apr 13 17:40:08 Ishaan-PC kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Apr 13 17:40:08 Ishaan-PC kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!!
Apr 13 17:40:08 Ishaan-PC kernel: [drm:si_startup] *ERROR* radeon: failed initializing UVD (-1).
Apr 13 17:40:08 Ishaan-PC kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Apr 13 17:40:08 Ishaan-PC kernel: [drm] ib test on ring 1 succeeded in 0 usecs
Apr 13 17:40:08 Ishaan-PC kernel: [drm] ib test on ring 2 succeeded in 0 usecs
Apr 13 17:40:08 Ishaan-PC kernel: [drm] ib test on ring 3 succeeded in 0 usecs
Apr 13 17:40:08 Ishaan-PC kernel: [drm] ib test on ring 4 succeeded in 0 usecsI have been getting this error since kernel update since kernel 3.13.5, present kernel is 3.14.0-5. Sometimes system just hangs when shutting down.
My VGA details:
lspci -k | grep -A3 VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
Subsystem: Dell Device 0572
Kernel driver in use: i915
Kernel modules: i915
--
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Chelsea LP [Radeon HD 7730M] (rev ff)
Kernel driver in use: radeon
Kernel modules: radeon
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)I have an integrated intel HD4000 and AMD HD7730m. The AMD gpu is turned off becuase of dpm being enabled since kernel 3.13 (thats what the wiki says), I am not using any methods to disable it manually.
I have also tried installing the catalyst-test-pxp from AUR but it boots to a blank screen and when i try to restart X, i get a segfault. Any solution?
EDIT: Kernel update 3.15.1-1-ARCH solved the problem.
Last edited by ishaanbahal (2014-07-04 07:16:27)
Offline
I met exact the same problem.
Offline
I met exact the same problem.
So what did you do??
Offline
I have the same problem too. And I have no ideas what I should do
Hey, I think you have the same laptop as me, Dell Inspiron 7520.
Maybe a kernel bug, and please post this thread to "Kernel & Hardware"
Last edited by gundamfj (2014-04-16 18:34:02)
Offline
I have the same problem too. And I have no ideas what I should do
Hey, I think you have the same laptop as me, Dell Inspiron 7520.Maybe a kernel bug, and please post this thread to "Kernel & Hardware"
Yes my laptop is a Dell Inspiron 7520 and its been happening since 4 kernel updates now. Now on 3.14.1-1 and still facing the same issue, infact the error shows up every time i see the console screen i.e shutdown, boot, suspend, resume and even log out!
Have you tried installing catalyst-test-pxp?
Offline
Hi.
Same Laptop (Dell 7520), same problem. The catalyst driver is not the best option on a rollin release...
Offline
Same laptop here, I get this error, but when I run:
DRI_PRIME=1 glxspheres64Graphic card seems to be working fine, since it runs at 200+ fps.
With:
DRI_PRIME=0 glxspheres64I get ~60 fps.
Offline
gundamfj wrote:I have the same problem too. And I have no ideas what I should do
Hey, I think you have the same laptop as me, Dell Inspiron 7520.Maybe a kernel bug, and please post this thread to "Kernel & Hardware"
Yes my laptop is a Dell Inspiron 7520 and its been happening since 4 kernel updates now. Now on 3.14.1-1 and still facing the same issue, infact the error shows up every time i see the console screen i.e shutdown, boot, suspend, resume and even log out!
Have you tried installing catalyst-test-pxp?
NO, I never use beta version driver
Offline
found 2 bug reports
https://bugs.freedesktop.org/show_bug.cgi?id=77244
https://bugzilla.kernel.org/show_bug.cgi?id=71891
Last edited by gundamfj (2014-04-19 08:12:14)
Offline
Same laptop here, I get this error, but when I run:
DRI_PRIME=1 glxspheres64Graphic card seems to be working fine, since it runs at 200+ fps.
With:
DRI_PRIME=0 glxspheres64I get ~60 fps.
So the issue just disappears?? If so I will try this..
The bug report seems to be active, so we will have to wait for a while for the patch... Although there is a proposed patch that seems to remove the UVD error, have you tried it??
Last edited by ishaanbahal (2014-04-19 08:59:55)
Offline
hjpbarcelos wrote:Same laptop here, I get this error, but when I run:
DRI_PRIME=1 glxspheres64Graphic card seems to be working fine, since it runs at 200+ fps.
With:
DRI_PRIME=0 glxspheres64I get ~60 fps.
So the issue just disappears?? If so I will try this..
gundamfj wrote:The bug report seems to be active, so we will have to wait for a while for the patch... Although there is a proposed patch that seems to remove the UVD error, have you tried it??
I quote a comment "Nopes. It makes the UVD errors go away, but the boot still gets stuck at the same point. Everything hangs up, requiring me to do a hard reboot."
The patch did not fix the bug. Honestly, the bug has been there since kernel 3.11.
Offline
Any found a solution to this error??
I am still getting the same error with 3.14.4-1-ARCH kernel.
Offline
That bug report in the kernel tracker says it was fixed upstream, or so I understood, maybe try mainline? I will when i have time as i'm facing the same issue
Offline