| Summary: | Mandatory amdgpu DC on Polaris | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Dmitry <terapy-session> | ||||
| Component: | DRM/AMDgpu | Assignee: | Default DRI bug account <dri-devel> | ||||
| Status: | RESOLVED INVALID | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | medium | ||||||
| Version: | XOrg git | ||||||
| Hardware: | Other | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Dmitry
2018-06-18 10:00:30 UTC
It's a bit unclear what you're saying. Disabling DC (via amdgpu.dc=0?) worked with 4.16.13, but doesn't anymore with 4.17.2? Please attach the dmesg output from a good case and if possible from a bad case. Almost. The shutdown did not work on 4.16.13 and earlier. And there is now on my fresh 4.17.2. Disable by removing amdgpu.dc=1 of the string. P.S. I noticed that there is a bug and when you disable TearFree in the config. Created attachment 140192 [details]
dmesg
(In reply to Dmitry from comment #2) > Almost. The shutdown did not work on 4.16.13 and earlier. And there is now > on my fresh 4.17.2. What is there now? > Disable by removing amdgpu.dc=1 of the string. DC is enabled by default as of 4.17, you have to explicitly disable it with amdgpu.dc=0. > P.S. I noticed that there is a bug and when you disable TearFree in the > config. Please file a separate report about that against product xorg, component Driver/AMDgpu. >> What is there now? Same thing. The system is not loaded beyond the point "Reached target graphic Interface". But there is one point, helps pressing Enter, sometimes two presses. >> DC is enabled by default as of 4.17, you have to explicitly disable it with amdgpu.dc=0. I understood the update meant that it was no longer necessary to specify startup parameters such as amdgpu.dc=1. Tried with amdgpu.dc=0, but the same problem. Found out that this bug with SDDM which I use. It is happening because of a change in configuration or any other reason. Sorry. Indeed the problem was on the SDDM side. Decided to install haveged. |
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.