From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107154] [drm] GPU recovery disabled.
Date: Sun, 08 Jul 2018 19:00:26 +0000 [thread overview]
Message-ID: <bug-107154-502-1OdX7sNzhy@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107154-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1224 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107154
--- Comment #1 from dwagner <jb5sgc1n.nya@20mm.eu> ---
Indeed, crashes upon S3 resumes have been abundant with amdgpu.dc=1 for many
months now, and seemingly for more than one reason.
One bug I reported in August 2017 with
https://bugs.freedesktop.org/show_bug.cgi?id=102323 - that one was fixed
quickly.
The next S3 resume crash I reported in October 2017 in
https://bugs.freedesktop.org/show_bug.cgi?id=103277, that one stayed without
any resolution until April 2018, and the fix found in that report only works if
no "drm.edid_firmware=..." kernel command line option is used.
Another crash bug with S3 resumes I reported for 4.17.2 kernels in
https://bugs.freedesktop.org/show_bug.cgi?id=107065 - then realized that 4.18
pre-releases exhibit the very same kind of crash immediately upon starting X11.
For this crash upon X11 startup, there is a patch in the bug report, but it
does not prevent the S3 resume crash.
I currently work around S3 resume crashes by switching to the console display
before enterin S3 sleep - but this is really an awkward work-around.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2630 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-07-08 19:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 9:24 [Bug 107154] [drm] GPU recovery disabled bugzilla-daemon
2018-07-08 19:00 ` bugzilla-daemon [this message]
2018-07-08 20:03 ` bugzilla-daemon
2018-07-09 8:53 ` bugzilla-daemon
2018-07-09 11:31 ` bugzilla-daemon
2018-07-09 16:03 ` bugzilla-daemon
2018-07-09 16:04 ` bugzilla-daemon
2018-07-09 16:13 ` bugzilla-daemon
2018-07-09 16:29 ` bugzilla-daemon
2018-07-10 7:04 ` bugzilla-daemon
2018-09-02 10:26 ` bugzilla-daemon
2018-09-11 13:38 ` 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-107154-502-1OdX7sNzhy@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;
as well as URLs for NNTP newsgroup(s).