dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 215436] admgpu: suspend and resuming from suspend don't work
Date: Tue, 04 Jan 2022 11:15:11 +0000	[thread overview]
Message-ID: <bug-215436-2300-p6vT7TbgFM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215436-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215436

spasswolf@web.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #300223|0                           |1
        is obsolete|                            |

--- Comment #21 from spasswolf@web.de ---
Created attachment 300224
  --> https://bugzilla.kernel.org/attachment.cgi?id=300224&action=edit
new debuggin patch

Seems the call trace of rn_vbios_smu_set_dcn_low_power is
amdgpu_dm_atomic_commit_tail -> dc_commit_state -> dc_commit_state_nocheck ->
dcn20_optimize_bandwith -> rn_update_clocks -> rn_vbios_smu_set_dcn_low_power

  53.562322] amdgpu 0000:08:00.0: amdgpu: Calling dc_commit_state from
amdgpu_dm_atomic_commit_tail
[   53.562426] amdgpu 0000:08:00.0: amdgpu: Calling dc_commit_state from
amdgpu_dm_atomic_commit_tail
[   53.563183] wlp4s0: deauthenticating from 54:67:51:3d:a2:e0 by local choice
(Reason: 3=DEAUTH_LEAVING)
[   53.673655] amdgpu 0000:08:00.0: amdgpu: Calling optimize_bandwidth from
dc_commit_state_no_check
[   53.673669] amdgpu 0000:08:00.0: amdgpu: Calling update_clocks from
dcn20_optimize_bandwidth
[   53.673672] amdgpu 0000:08:00.0: amdgpu: adev->in_s0ix = 0
[   53.673673] amdgpu 0000:08:00.0: amdgpu: calling
rn_vbios_smu_set_dcn_low_power
[   53.674562] amdgpu 0000:08:00.0: amdgpu: Calling dc_commit_state from
amdgpu_dm_atomic_commit_tail

This seems to be not really connected to suspend.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-01-04 11:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29 12:28 [Bug 215436] New: admgpu: suspend and resuming from suspend don't work bugzilla-daemon
2021-12-29 15:08 ` [Bug 215436] " bugzilla-daemon
2021-12-29 15:10 ` bugzilla-daemon
2021-12-30 13:03 ` bugzilla-daemon
2021-12-30 13:16 ` bugzilla-daemon
2021-12-30 14:33 ` bugzilla-daemon
2021-12-31  0:17 ` bugzilla-daemon
2021-12-31  0:22 ` bugzilla-daemon
2021-12-31 15:10 ` bugzilla-daemon
2021-12-31 16:14 ` bugzilla-daemon
2022-01-01  1:42 ` bugzilla-daemon
2022-01-03  9:29 ` bugzilla-daemon
2022-01-03  9:35 ` bugzilla-daemon
2022-01-03  9:36 ` bugzilla-daemon
2022-01-03 10:20 ` bugzilla-daemon
2022-01-03 10:29 ` bugzilla-daemon
2022-01-03 15:48 ` bugzilla-daemon
2022-01-03 17:12 ` bugzilla-daemon
2022-01-03 17:49 ` bugzilla-daemon
2022-01-03 17:51 ` bugzilla-daemon
2022-01-04 10:17 ` bugzilla-daemon
2022-01-04 10:25 ` bugzilla-daemon
2022-01-04 11:15 ` bugzilla-daemon [this message]
2022-01-04 11:27 ` bugzilla-daemon
2022-01-04 14:14 ` bugzilla-daemon
2022-01-04 14:59 ` bugzilla-daemon
2022-01-04 15:03 ` bugzilla-daemon
2022-01-04 15:27 ` bugzilla-daemon
2022-01-04 15:28 ` bugzilla-daemon
2022-01-24 22:45 ` bugzilla-daemon
2022-01-25 20:25 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-215436-2300-p6vT7TbgFM@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).