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: Sun, 15 Oct 2017 17:24:43 +0000 [thread overview]
Message-ID: <bug-103277-502-IwHyZcbA2X@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103277-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1822 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103277
--- Comment #2 from Jordan L <jordan.lazare@amd.com> ---
(In reply to dwagner from comment #0)
> After I updated my kernel to
> https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next as of
> today (latest commit at this time:
> 1c630e83443a0f271c192ecfa0d94023661a0000) I noticed that my computer would
> no longer wake up from S3 sleep - power LED goes on, but apart from that no
> display and no reaction to any input (other than Num-Lock still switchable).
>
> The difference to the ~2 weeks older kernel was 100% reproducable by just
> doing:
>
> - boot to console (no start of X11 required) and login as root
> - echo "mem" >/sys/power/state
> - wait till power LED blinks
> - press some key to wake up the system
> - observe no display output and no reaction to anything
>
> GPU is a RX 460, CPU a Ryzen R7 1800X, board Asus X370 Pro, connected is one
> 4k display via HDMI 2.0.
>
> I bisected the git commits, and the one that causes the bug is:
>
> > 7ae4acd21e9e264afb079e23d43bcf2238c7dbea
> > drm/amd/display: Match actual state during S3 resume.
>
> After this, I went back to the current HEAD of amd-staging-drm-next and
> (manually) reverted only commit 7ae4acd21e9e264afb079e23d43bcf2238c7dbea,
> and this indeed results in a kernel that works fine with regards to resuming
> from S3 sleep.
>
> There are no noteworthy "dmesg"-emissions that accompany going to S3 sleep,
> but the dmesg-output that I can collect ends slightly before the system
> actually sleeps, so wether anything is emitted upon the wake-up attempt, I
> have no way to know.
Thanks, we can reproduce this too, should have something shortly.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3005 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
next prev parent reply other threads:[~2017-10-15 17:24 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 [this message]
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
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-IwHyZcbA2X@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox