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, 24 Apr 2018 21:35:07 +0000 [thread overview]
Message-ID: <bug-103277-502-CeNlAttIWD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103277-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 912 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103277
--- Comment #22 from dwagner <jb5sgc1n.nya@20mm.eu> ---
Two patches posted by Harry Wentland in bug report
https://bugs.freedesktop.org/show_bug.cgi?id=106159
today may hold the key to get finally rid of this long-standing bug:
When I apply
https://bugs.freedesktop.org/attachment.cgi?id=139069
and
https://bugs.freedesktop.org/attachment.cgi?id=139070
on top of
"commit ecdd681a62f592e03c3783709526278bdc7ad5cc (HEAD,
origin/drm-next-4.18-wip)"
_then_ I can S3-resume without crashing with amdgpu.dc=1
_But_ the system will still crash on S3-resume if I use the
"drm.edid_firmware=edid/LG_EG9609_edid.bin"
kernel command line option (which I would like to use to make X11 mode
detection independent of whether the connected TV is off when booting/resuming)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2213 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:[~2018-04-24 21:35 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
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 [this message]
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-CeNlAttIWD@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.