Bug 106054 - [vega10] powerplay non critical errors on vega 56 with vega 64bios
Summary: [vega10] powerplay non critical errors on vega 56 with vega 64bios
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-15 10:25 UTC by Tom Englund
Modified: 2019-11-19 08:35 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Tom Englund 2018-04-15 10:25:27 UTC
Hi so i have flashed the vega 64bios onto my 56 vega for the ramped up memory voltage so i can run the core at ~1630mhz and mem at ~995 mhz, works fine in both windows and linux, however i noticed some errors from powerplay in dmesg at boot doing so. havent noticed any issue about it but thought il report them anyways.

Radeon RX Vega (VEGA10, DRM 3.25.0, 4.16.0-rc7-gc698ca527893, LLVM 7.0.0)
Mesa 18.1.0-devel (git-6a519a157b)

[   14.816394] amdgpu: [powerplay] Cannot find UCLK in SOC_VDD-UCLK Dependency Table!
[   14.816395] amdgpu: [powerplay] Failed to populate MCLK during PopulateNewDPMClocksStates Function!
[   14.816395] amdgpu: [powerplay] Failed to populate and upload SCLK MCLK DPM levels!
[   47.262630] amdgpu: [powerplay] Cannot find UCLK in SOC_VDD-UCLK Dependency Table!
[   47.262631] amdgpu: [powerplay] Failed to populate MCLK during PopulateNewDPMClocksStates Function!
[   47.262631] amdgpu: [powerplay] Failed to populate and upload SCLK MCLK DPM levels!
[   47.264054] amdgpu: [powerplay] Cannot find UCLK in SOC_VDD-UCLK Dependency Table!
[   47.264054] amdgpu: [powerplay] Failed to populate MCLK during PopulateNewDPMClocksStates Function!
[   47.264055] amdgpu: [powerplay] Failed to populate and upload SCLK MCLK DPM levels!
Comment 1 Alex Deucher 2018-04-16 13:41:57 UTC
Flashing random vbioses is not supported and will likely void your warranty.
Comment 2 Tom Englund 2018-04-16 14:40:27 UTC
oh i know :), just thought it maybe might be useful to know about or look at if there is something wrong in the driver, but i fully accept its my own fault if otherwise :D
Comment 3 Martin Peres 2019-11-19 08:35:16 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/345.


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.