All of lore.kernel.org
 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 10:17:36 +0000	[thread overview]
Message-ID: <bug-215436-2300-YDfk4SAg52@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215436-2300@https.bugzilla.kernel.org/>

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

--- Comment #19 from spasswolf@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.

  parent reply	other threads:[~2022-01-04 10:17 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 [this message]
2022-01-04 10:25 ` bugzilla-daemon
2022-01-04 11:15 ` bugzilla-daemon
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-YDfk4SAg52@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.