Summary: | DC, Powerplay, Tonga, top screen flicker with current amd-staging-4.9 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Andy Furniss <adf.lists> | ||||||
Component: | DRM/AMDgpu | Assignee: | Jordan L <jordan.lazare> | ||||||
Status: | RESOLVED FIXED | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | medium | CC: | harry.wentland | ||||||
Version: | DRI git | ||||||||
Hardware: | Other | ||||||||
OS: | All | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Andy Furniss
2017-03-25 18:22:31 UTC
So this doesn't happen with amdgpu.dc=0? (In reply to Michel Dänzer from comment #1) > So this doesn't happen with amdgpu.dc=0? It's OK with amdgpu.dc=0 Created attachment 130499 [details] dmesg dmesg attached, plus a link to an external video of what it looks like. As seen it's also visible when playing a vid, mpv is using opengl for output. https://drive.google.com/file/d/0BxP5-S1t9VEEak90Tk9wM2dUVlU/view?usp=sharing Can you try finishing the bisect once again? Just continue with git bisect skip until it either finds the regression commit or prints the minimal range of candidate commits. Seems, I've found it. Many skips to work around vega build issues, but I got past them and got a bad then good. Further skips then due to startx hangs with dmesg logging ring test fails on 3 to 8. Fortunately it then worked and only gave two choices one vega and - possible first bad commit: [91561a39fa74e79b88e0e9d70f3072501c8df2ce] drm/amdgpu: get display info from DC when DC enabled. This cleanly reverts from head - and the issue is gone with it reverted. # skip: [4513c8c07e243b77a36192a3c49845f85a656cea] drm/amd/display: Remove DCE12 guards git bisect skip 4513c8c07e243b77a36192a3c49845f85a656cea # bad: [76cfd18b173dd61d24de2c28fa92443fcfe165d8] drm/amdgpu: gart fixes for vega10 git bisect bad 76cfd18b173dd61d24de2c28fa92443fcfe165d8 # good: [6c59cf82dac54970284b3126ff9a15b6b0de6108] drm/amdgpu: add vega10 chip name git bisect good 6c59cf82dac54970284b3126ff9a15b6b0de6108 # skip: [9a493aa52c3a5176acd7b8ec32b66dc58bded8b2] drm/amdgpu: use atomfirmware interfaces for scratch reg save/restore git bisect skip 9a493aa52c3a5176acd7b8ec32b66dc58bded8b2 # skip: [d0a2e62fca3e502951bd1eb392e5331ad80dc88c] drm/amdgpu: add IV trace point git bisect skip d0a2e62fca3e502951bd1eb392e5331ad80dc88c # skip: [40610a13a747afacb17fa2b9decfa8e5455671b4] drm/amdgpu: add 64bit doorbell assignments git bisect skip 40610a13a747afacb17fa2b9decfa8e5455671b4 # good: [d9693ee35fd55106b70bbd1dae9ce71b578ab3e9] drm/amdgpu: add psp firmware header info git bisect good d9693ee35fd55106b70bbd1dae9ce71b578ab3e9 # only skipped commits left to test # possible first bad commit: [76cfd18b173dd61d24de2c28fa92443fcfe165d8] drm/amdgpu: gart fixes for vega10 # possible first bad commit: [91561a39fa74e79b88e0e9d70f3072501c8df2ce] drm/amdgpu: get display info from DC when DC enabled. Thanks, Andy, for the report and taking the time to bisect. Jordan from my team spotted the bug as well and is working on a solution. If you're curious about the cause of this... The gist of it is that we don't fill in some info for pplib on DCE 8 and 10 because we don't have the full bandwidth formula implemented. So we either have to fill in some reasonable values or make sure DCE 8 and 10 use the old codepath. Hope to have a fix soon. Created attachment 130628 [details] [review] Fix for Tonga screen flicker issue Hi Andy, This patch should fix the issue. Thanks, Jordan Hi. The patch fixes the issue for me. Bit cheeky - but I won't know if I don't ask, and I guess the DAL team didn't see a bug I filed a year ago. Maybe it's not a bug but a feature request - In summary when I use DC I loose CEA interlaced modes for my HDMI TV. I do have a use case for these, but may well be in a very small minority in that :-) https://bugs.freedesktop.org/show_bug.cgi?id=94679 Thanks for pointing us to your other issue. Left a comment there. Fix is now in agd5f amd-staging-4.9. |
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.