Bug 91371 - UVD not responding error during UVD initialization for AMD 7670M graphics
Summary: UVD not responding error during UVD initialization for AMD 7670M graphics
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-15 19:29 UTC by Arun George
Modified: 2015-01-22 15:50 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.16
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg (67.79 KB, text/plain)
2015-01-15 19:29 UTC, Arun George
Details
xorg log (44.62 KB, text/plain)
2015-01-15 19:30 UTC, Arun George
Details

Description Arun George 2015-01-15 19:29:50 UTC
Created attachment 163551 [details]
dmesg

My Linux Kernel version is 3.16.7 .My System is a HP Pavillion g6 laptop with AMD A8-4500M APU with 7640G + 7670M Dual Graphics.On booting Manjaro (and Ubuntu) distro i get these errors and display blinks before and after showing them. 

[   26.971983] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   27.992402] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   29.012898] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   30.033439] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   31.053953] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   32.074424] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   33.094895] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   34.115369] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   35.135841] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   36.156319] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   36.176381] [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!!
[   36.176432] [drm:evergreen_startup] *ERROR* radeon: error initializing UVD (-1).
[   37.611579] [drm:radeon_acpi_init] *ERROR* Cannot find a backlight controller

I found some cards reported having these errors earlier in 3.13 kernel but it was found to be fixed in 3.15 (dont know if this is a reccurence of that bug).
The UVD initialization for integrated card seems to be fine while UVD fails for Dedicated card.Currently the problems faced due to this are that booting succeeds randomly(sometimes it gives a black screen sometimes it gets stuck before login screen) and when it does the booting time is high.

It also shows these errors during shutdown.I tried to turn off dpm ,but that gave me a blank screen(and not able to load X).I tried other kernels and it persists in 3.17 and 3.18 kernels.
Comment 1 Arun George 2015-01-15 19:30:44 UTC
Created attachment 163561 [details]
xorg log
Comment 2 Adis Hamzić 2015-01-21 11:32:54 UTC
Have the same issue since my kernel update yesterday. It happens roughly every other boot. Most times it still manages to boot, despite the error, but the performance makes the system unusable.
Here are some details:

$ uname -srm
Linux 3.14.28-1-MANJARO x86_64

$ lspci -k | grep -A3 VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X]
	Subsystem: Gigabyte Technology Co., Ltd Device 2267
	Kernel driver in use: radeon
	Kernel modules: radeon

Jan 21 11:07:46 adis-pc kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Jan 21 11:07:47 adis-pc kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Jan 21 11:07:48 adis-pc kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Jan 21 11:07:49 adis-pc kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Jan 21 11:07:50 adis-pc kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Jan 21 11:07:51 adis-pc kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Jan 21 11:07:53 adis-pc kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Jan 21 11:07:54 adis-pc kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Jan 21 11:07:55 adis-pc kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Jan 21 11:07:56 adis-pc kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Jan 21 11:07:56 adis-pc kernel: [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!!
Jan 21 11:07:56 adis-pc kernel: [drm:si_startup] *ERROR* radeon: failed initializing UVD (-1).
Comment 3 Michel Dänzer 2015-01-22 01:51:06 UTC
(In reply to Adis Hamzić from comment #2)
> Have the same issue since my kernel update yesterday.

What kernel version did you update from? Can you bisect?
Comment 4 Adis Hamzić 2015-01-22 10:47:08 UTC
(In reply to Michel Dänzer from comment #3)
> (In reply to Adis Hamzić from comment #2)
> > Have the same issue since my kernel update yesterday.
> 
> What kernel version did you update from? Can you bisect?

According to the logs it's was 3.14.27, but I can't see anything in the diff that relates to radeon:

[2015-01-19 19:54] [ALPM] upgraded linux314 (3.14.27-1 -> 3.14.28-1)

I'll try to compile and install the old version and see if the issue is still there.
Comment 5 Adis Hamzić 2015-01-22 15:50:45 UTC
I just tested the kernels 3.14.27 and 3.16.7.3 and they both display the issue. 

Now, I had used the 3.14.27 kernel for at least 10 days and I never noticed this issue. In that time I was doing some kernel debugging which involved a great number of cold and hard reboots so I think I would have noticed the issue if it had been there. I'll test some older kernels soon.

What I found out during my testing was:
 * Setting radeon.dpm=0 fixes the issue.
 * Doing a hard reboot / poweroff has a very high chance of triggering the problem, in fact I managed to reproduce it 10 consecutive times.
 * Doing a soft reboot has very little chance of triggering the problem. With this I managed to have 10 consecutive successful boots.

Note You need to log in before you can comment on or make changes to this bug.