[Bug 215436] admgpu: suspend and resuming from suspend don't work
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Tue Jan 4 10:17:36 UTC 2022
https://bugzilla.kernel.org/show_bug.cgi?id=215436
--- Comment #19 from spasswolf at web.de ---
Created attachment 300222
--> https://bugzilla.kernel.org/attachment.cgi?id=300222&action=edit
debugging patch
I added some more dev_info calls to figure out where things are called:
[ 34.946911] wlp4s0: deauthenticating from 54:67:51:3d:a2:e0 by local choice
(Reason: 3=DEAUTH_LEAVING)
[ 35.079021] amdgpu 0000:08:00.0: amdgpu: Calling update_clocks from
dcn10_set_clock
[ 35.079026] amdgpu 0000:08:00.0: amdgpu: adev->in_s0ix = 0
[ 35.079027] amdgpu 0000:08:00.0: amdgpu: calling
rn_vbios_smu_set_dcn_low_power
[ 39.030889] PM: suspend entry (s2idle)
[ 39.270864] Filesystems sync: 0.239 seconds
[ 39.271929] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 39.274694] OOM killer disabled.
The WLAN message is the first message one gets after initiating suspend. The
interesting thing is that rn_vbios_set_dc_low_power is called before suspend
entry (and there's also a long 4s gap).
I also have no idea where dcn10_set_clock is called. The only place I found
is from within dc_set_clock, but dc_set_clock is called nowhere in the entire
amdgpu module.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
More information about the dri-devel
mailing list