Bug 91486 - [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Summary: [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2015-07-28 10:52 UTC by Mike Lothian
Modified: 2015-09-11 18:21 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Dmesg (68.50 KB, text/plain)
2015-07-28 10:52 UTC, Mike Lothian
no flags Details
Xorg log when X wouldn't start (46.01 KB, text/plain)
2015-07-28 11:14 UTC, Mike Lothian
no flags Details

Description Mike Lothian 2015-07-28 10:52:20 UTC
Created attachment 117414 [details]

I've started getting the above errors when the GPU is initialised on my PRIME system. It seems a bit suspicious that uvd v1 is being initialised as this is a Radeon 6xxx series GPU. Since hitting this issue I can't boot into windows without a BSOD pointing to the ati driver.

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] [1002:6741] (rev ff)

I'm attaching the dmesg
Comment 1 Mike Lothian 2015-07-28 10:54:57 UTC
I should add that I can get a DRI_PRIME=1 glxinfo to work (it does take longer than usual) but when I to a DRI_PRIME=1 glxgears I just get garbage rendered and the machine locks up shortly after this
Comment 2 Mike Lothian 2015-07-28 11:13:57 UTC
I'm going to try an older kernel just in case but I'm worried this might be hardware failure

The last time I booted up X would start but then the machine would freeze up

Had to boot with radeon.dpm=0 radeon.runpm=0 radeon.modeset=0 to get X to start
Comment 3 Mike Lothian 2015-07-28 11:14:33 UTC
Created attachment 117415 [details]
Xorg log when X wouldn't start
Comment 4 Mike Lothian 2015-09-11 13:46:13 UTC
My laptop has went to the big enrichment centre in the sky

Seems the issues I was seeing were the first signs of that, now I don't even get as far as the BIOS
Comment 5 Christian König 2015-09-11 18:21:02 UTC
Sorry to hear that.

Since you couldn't boot windows any more either the conclusion that's something wrong with the hardware was not to far to seek.

Going to keep that in mind when other people see similar issues.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.