<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#c32">Comment # 32</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#c29">comment #29</a>) > 2) The inconsistend dpm behaviour between dc=1 and dc=0 is still a thing. > force_atpx=1 plus dc=1 gives me wonderful dpm with the dGPU fully powering > down between uses. force_atpx=1 plus dc=0 does not. No idea what's up with > that. The platform claims to have an eDP panel connected, apparently even in hybrid graphics mode when it's not actually in use. The non-DC code assumes that if there is an eDP panel, it's always connected since it's a non-removable display and it shouldn't be present if there isn't one. Because the driver thinks a display is connected, the dGPU is kept on.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>