From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199693] System freeze after resuming from suspend (amdgpu)
Date: Tue, 15 May 2018 09:41:01 +0000 [thread overview]
Message-ID: <bug-199693-2300-hs6HBbbiaQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199693-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199693
Thomas Martitz (kugel@rockbox.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |kugel@rockbox.org
Resolution|DUPLICATE |---
--- Comment #2 from Thomas Martitz (kugel@rockbox.org) ---
This is not the same as bug 199609 I'm afraid. This bug describes a behavior
where the very first resume.
However, if I make a fix (I'll post it later this day hopefully) for this bug,
then I start seeing bug 199609 too.
In fact, amdgpu developers asked me to file a bug report against the kernel
while bug 199609 was moved to amdgpu.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-15 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199693-2300@https.bugzilla.kernel.org/>
2018-05-15 7:27 ` [Bug 199693] System freeze after resuming from suspend (amdgpu) bugzilla-daemon
2018-05-15 9:41 ` bugzilla-daemon [this message]
2018-05-15 9:41 ` bugzilla-daemon
2018-05-15 9:42 ` bugzilla-daemon
2018-05-15 15:26 ` [Bug 199693] [bisect 08810a4119aaebf6318f209ec5dd9828e969cba4] (pci runtime) " bugzilla-daemon
2018-05-15 19:14 ` bugzilla-daemon
2018-05-15 19:16 ` bugzilla-daemon
2018-05-17 16:26 ` 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-199693-2300-hs6HBbbiaQ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.