Priority | medium |
---|---|
Bug ID | 77244 |
Assignee | dri-devel@lists.freedesktop.org |
Summary | UVD microcode fails to load on HD 8970M (Neptune XT -- PITCAIRN) |
Severity | normal |
Classification | Unclassified |
OS | All |
Reporter | nmschulte@gmail.com |
Hardware | Other |
Status | NEW |
Version | unspecified |
Component | DRM/Radeon |
Product | DRI |
Created attachment 97143 [details] Linux kernel log I have a Clevo P150SM based laptop with an Intel HD 4600 iGPU and an AMD Radeon HD 8970M dGPU. I receive the following errors when the Radeon DRI/DRM implementation attempts to initialize the card: [ 65.525470] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 66.537637] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 67.549797] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 68.561967] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 69.574142] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 70.586334] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 71.598533] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 72.610705] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 73.622877] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 74.635068] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 74.654938] [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!! [ 74.654955] [drm:si_startup] *ERROR* radeon: failed initializing UVD (-1). This appears to happen on video mode changes or vtty changes, I'm not quite sure really what triggers it other than initial loading. When it does occur, the system appears to hang for a short time (15 seconds or so) while the dGPU is active, and then "comes back" after the dGPU is disabled. The Clevo P150SM has an LED showing the dGPU power state, and debugfs/vgaswitcheroo seems to corroborate this. I'm also experiencing issues with PRIME (and e.g. xserver seg-faults when building from source to try new code), but this issue exists out of the box on Debian Sid, and seems to persist even with newer Mesa and DRM. I have a bug report for the PRIME/hybrid graphics issue as well, and it may end up that these are related: https://bugs.freedesktop.org/show_bug.cgi?id=77094 Finally, this bug looks similar to mine, though I am not messing with PRIME (at least explicitly; no xrandr --setprovider* calls and no DRI_PRIME env. var. is set): https://bugs.freedesktop.org/show_bug.cgi?id=75234 There is a downstream bug report here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743659
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel