Bug 108570 - AMDGPU DC not working on PCI Express 2.0?
Summary: AMDGPU DC not working on PCI Express 2.0?
Status: RESOLVED NOTABUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-26 16:15 UTC by TestMode11
Modified: 2018-10-26 17:06 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg-amd (49.88 KB, text/plain)
2018-10-26 16:43 UTC, TestMode11
no flags Details

Description TestMode11 2018-10-26 16:15:24 UTC
On RX560 I get the following in dmesg

[    8.426625] kfd kfd: skipped device 1002:67ef, PCI rejects atomics

Then in Weston start log I do not see "DRM supports atomic modesetting". 

Does this mean that DC is not active? Do AMDGPU DC and atomic modesetting only work with PCI Express 3.0?
Comment 1 John Bridgman 2018-10-26 16:22:34 UTC
I don't believe there is any connection between "atomic" modesetting and atomic operations in PCIE 3.0.

Do you see other DC-related messages ? Might be helpful to post your full dmesg output.
Comment 2 TestMode11 2018-10-26 16:43:39 UTC
Created attachment 142223 [details]
dmesg-amd
Comment 3 TestMode11 2018-10-26 16:44:45 UTC
Not seeing any DC success or error messages - though not clear how these would look.
Comment 4 Alex Deucher 2018-10-26 17:06:17 UTC
(In reply to TestMode11 from comment #0)
> On RX560 I get the following in dmesg
> 
> [    8.426625] kfd kfd: skipped device 1002:67ef, PCI rejects atomics

That message is from kfd.  It's for ROCm.  Unrelated to DC

> 
> Then in Weston start log I do not see "DRM supports atomic modesetting". 
> 
> Does this mean that DC is not active? Do AMDGPU DC and atomic modesetting
> only work with PCI Express 3.0?

No, DC has nothing to do with pci atomics.  DC is enabled:
[    8.690697] [drm] Display Core initialized with v3.2.02!


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.