Bug 101491 - Can't wake up the dedicated graphics card unless power management is disabled
Summary: Can't wake up the dedicated graphics card unless power management is disabled
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2017-06-18 19:28 UTC by drkdfndr
Modified: 2019-11-19 09:29 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

dmesg output (87.89 KB, text/plain)
2017-06-18 19:28 UTC, drkdfndr
no flags Details
lspci -k output (3.77 KB, text/plain)
2017-06-18 19:29 UTC, drkdfndr
no flags Details
add workaround (1.24 KB, patch)
2017-06-19 16:55 UTC, Alex Deucher
no flags Details | Splinter Review

Description drkdfndr 2017-06-18 19:28:02 UTC
Created attachment 132031 [details]
dmesg output

I have a ASUS K53TK with a AMD A6-3420M. It has an integrated graphics card the AMD HD 6520G, and a dedicated one HD 7670M.
I am only able to use the dedicated card if I set the parameter "radeon.runpm=0".
Otherwise xrandr only sees one provider, and DRI_PRIME=1 can't render any program.

At boot time, if I don't disable the power management I get several error like [  458.460874] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xFFFFFFFF).
Comment 1 drkdfndr 2017-06-18 19:29:24 UTC
Created attachment 132032 [details]
lspci -k output
Comment 2 Alex Deucher 2017-06-19 16:55:54 UTC
Created attachment 132063 [details] [review]
add workaround

PX is known to be broken on K53TK systems.  Add a quirk for another variant.
Comment 3 Martin Peres 2019-11-19 09:29:21 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/803.

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.