From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 77244] New: UVD microcode fails to load on HD 8970M (Neptune XT -- PITCAIRN) Date: Wed, 09 Apr 2014 16:26:47 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0537228093==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id D9E2D6E06C for ; Wed, 9 Apr 2014 09:26:47 -0700 (PDT) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0537228093== Content-Type: multipart/alternative; boundary="1397060807.5c2e24D0.24157"; charset="us-ascii" --1397060807.5c2e24D0.24157 Date: Wed, 9 Apr 2014 16:26:47 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=77244 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 --> https://bugs.freedesktop.org/attachment.cgi?id=97143&action=edit 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. --1397060807.5c2e24D0.24157 Date: Wed, 9 Apr 2014 16:26:47 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"
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.
--1397060807.5c2e24D0.24157-- --===============0537228093== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0537228093==--