All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103277] [bisected] Systems hangs on resume from S3 sleep due to "Match actual state during S3 resume" commit
Date: Tue, 20 Feb 2018 23:53:11 +0000	[thread overview]
Message-ID: <bug-103277-502-Z03rT6pWiE@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103277-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2892 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=103277

--- Comment #16 from dwagner <jb5sgc1n.nya@20mm.eu> ---
I noticed in the git log of amd-staging-drm-next that multiple patches
were committed that might be related to S3 resumes, so I retried whether
a kernel compiled from the current amd-staging-drm-next head is able to
resume from S3.

Unluckily, the symptoms are unchanged: System crashes upon every S3 resume
attempt - so I'm back to the kernel from last October that resumes fine.

With relevant security issues having been addressed in the kernel
between Oct 17 and now this situation becomes unbearable for me.

Patches that were included in the kernel I tried today:

> commit f8c80313f7a6a8f66b74b118b0e3e5112718e2e5 (HEAD, origin/amd-staging-drm-next)
> Author: Alex Deucher <alexander.deucher@amd.com>
> Date:   Thu Feb 15 08:40:30 2018 -0500
>   Revert "drm/radeon/pm: autoswitch power state when in balanced mode"
>   This reverts commit 1c331f75aa6ccbf64ebcc5a019183e617c9d818a.
>   Breaks resume on some systems.

> commit 734b7ebc0e16b0fb4d2937cc3716c505d7e2c319
> Author: Hersen Wu <hersenxs.wu@amd.com>
> Date:   Tue Jan 30 11:46:16 2018 -0500
> 
>   drm/amd/display: VGA black screen from s3 when attached to hook    
>    [Description] For MST, DC already notify MST sink for MST mode, DC stll
>    check DP SINK DPCD register to see if MST enabled. DP RX firmware may
>    not handle this properly.

> commit adf1c840a6741f1b53ecd6e466e160c725a80641
> Author: Yongqiang Sun <yongqiang.sun@amd.com>
> Date:   Fri Feb 2 17:35:00 2018 -0500
>   drm/amd/display: Keep eDP stream enabled during boot.
>   
>   This path fixed specific eDP panel cold boot black screen
>   due to unnecessary enable link.
>   Change:
>   In case of boot up with eDP, if OS is going to set mode
>   on eDP, keep eDP light up, do not disable and reset corresponding
>   HW.
>   This change may affect dce asics and S3/S4 Resume with multi-monitor.

> commit 8dd8b6bb22fb2470af4e8743f19eabba8127d566
> Author: Charlene Liu <charlene.liu@amd.com>
> Date:   Wed Jan 24 13:18:57 2018 -0500
> 
>  drm/amd/display: resume from S3 bypass power down HW block.

> commit 8d0de6a585e2186734748be2a1043eb3456ed8ed
> Author: Mikita Lipski <mikita.lipski@amd.com>
> Date:   Sat Feb 3 15:19:20 2018 -0500
>   drm/amdgpu: Unify the dm resume calls into one
>  
>   amdgpu_dm_display_resume is now called from dm_resume to
>   unify DAL resume call into a single function call
>   
>   There is no more need to separately call 2 resume functions
>   for DM.
>   
>   Initially they were separated to resume display state after
>   cursor is pinned. But because there is no longer any corruption
>   with the cursor - the calls can be merged into one function hook.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4365 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-02-20 23:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-14 16:06 [Bug 103277] [bisected] Systems hangs on resume from S3 sleep due to "Match actual state during S3 resume" commit bugzilla-daemon
2017-10-14 16:06 ` bugzilla-daemon
2017-10-15 17:24 ` bugzilla-daemon
2017-11-11 18:41 ` bugzilla-daemon
2017-12-11 21:55 ` bugzilla-daemon
2017-12-12 23:10 ` bugzilla-daemon
2017-12-12 23:17 ` bugzilla-daemon
2017-12-12 23:18 ` bugzilla-daemon
2017-12-13  0:09 ` bugzilla-daemon
2017-12-13  0:22 ` bugzilla-daemon
2017-12-13 16:11 ` bugzilla-daemon
2018-01-20 13:38 ` bugzilla-daemon
2018-01-22 15:06 ` bugzilla-daemon
2018-01-22 23:08 ` bugzilla-daemon
2018-01-23  4:25 ` bugzilla-daemon
2018-01-23  4:28 ` bugzilla-daemon
2018-02-20 23:53 ` bugzilla-daemon [this message]
2018-02-21  2:12 ` bugzilla-daemon
2018-02-21 21:42 ` bugzilla-daemon
2018-03-15 15:07 ` bugzilla-daemon
2018-03-17 11:13 ` bugzilla-daemon
2018-03-17 11:18 ` bugzilla-daemon
2018-04-24 21:35 ` bugzilla-daemon
2018-04-24 21:35 ` bugzilla-daemon
2018-04-24 21:39 ` bugzilla-daemon
2018-04-25 15:04 ` bugzilla-daemon
2018-06-27 15:00 ` bugzilla-daemon
2018-06-28 19:51 ` bugzilla-daemon
2018-06-29  7:32 ` 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-103277-502-Z03rT6pWiE@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.