WHi Alex, On Thu, Apr 19, 2018 at 4:13 PM, Alex Deucher <alexdeucher at gmail.com> wrote: >>>> https://bugs.freedesktop.org/show_bug.cgi?id=105684 >>> >>> No progress made on that bug report so far. >>> What can we do to help this advance? >> >> Ping, any news here? How can we help advance on this bug? > > Can you try one of these branches? > https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next > https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.18-wip > do they work any better? It's been over 3 months since we reported this bug by email, over 6 weeks since we reported it on bugzilla, and still there has been no meaningful diagnostics help from AMD. This follows a similar pattern to what we have seen with other issues prior to this one. What can we do so that this bug gets some attention from your team? Secondarily https://bugs.freedesktop.org/show_bug.cgi?id=106228 is another bug that needs attention. We have a growing number of consumer platforms affected by this. When booted, the amdgpu screen brightness value is incorrectly read back as 0, which systemd will then store on shutdown. On next boot, it restores the very low brightness level. This can reproduce out of the box on Fedora, Ubuntu, etc. Thanks, Daniel
