From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111848] AMDGPU and display fails after resume from suspend
Date: Thu, 03 Oct 2019 14:38:08 +0000 [thread overview]
Message-ID: <bug-111848-502-bcfLYPiMRn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111848-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 294 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111848
--- Comment #15 from me@cschwarz.com ---
Is there a Fedora workflow for bisecting?
Also, do I need to take care of any GPU firmware or is it just the kernel?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1052 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-10-03 14:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-28 9:30 [Bug 111848] AMDGPU and display fails after resume from suspend bugzilla-daemon
2019-09-28 9:32 ` bugzilla-daemon
2019-09-28 9:32 ` bugzilla-daemon
2019-09-28 9:32 ` bugzilla-daemon
2019-09-28 9:33 ` bugzilla-daemon
2019-09-28 9:33 ` bugzilla-daemon
2019-09-28 9:34 ` bugzilla-daemon
2019-09-28 9:34 ` bugzilla-daemon
2019-09-28 9:34 ` bugzilla-daemon
2019-09-28 9:35 ` bugzilla-daemon
2019-09-28 9:35 ` bugzilla-daemon
2019-09-28 9:35 ` bugzilla-daemon
2019-09-28 9:36 ` bugzilla-daemon
2019-10-03 14:20 ` bugzilla-daemon
2019-10-03 14:31 ` bugzilla-daemon
2019-10-03 14:38 ` bugzilla-daemon [this message]
2019-10-03 14:40 ` bugzilla-daemon
2019-10-03 14:59 ` bugzilla-daemon
2019-10-04 18:27 ` bugzilla-daemon
2019-10-07 10:14 ` bugzilla-daemon
2019-11-19 9:56 ` 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-111848-502-bcfLYPiMRn@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