<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - (DC 4.15-rc2) WARNING: CPU: 4 PID: 75 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:601 dm_suspend+0x4e/0x60 [amdgpu]" href="https://bugs.freedesktop.org/show_bug.cgi?id=104064#c41">Comment # 41</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - (DC 4.15-rc2) WARNING: CPU: 4 PID: 75 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:601 dm_suspend+0x4e/0x60 [amdgpu]" href="https://bugs.freedesktop.org/show_bug.cgi?id=104064">bug 104064</a> from <a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> Alex Deucher</a> <pre>(In reply to taijian from <a href="show_bug.cgi?id=104064#c40">comment #40</a>) > OK, I hate to be necrobumping this, but I've continued to follow and test > drm-next-4.17-wip and it seems that not only has the backlight patch from > #34 not made it in yet, but also that the forced atpx option from #14 has > also disappeared after all of the vega12 additions. Soooo, are these things > going to come back? Sorry, my impression from <a href="show_bug.cgi?id=104064#c29">comment 29</a> was that messing the the OSI string fixed the issue. Is that not the case? Do you still need to force ATPX? If we, we can just add a quirk so the driver does it automatically.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>