From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209457] AMDGPU resume fail with RX 580 GPU
Date: Wed, 14 Oct 2020 21:08:40 +0000 [thread overview]
Message-ID: <bug-209457-2300-LfN1fjB1jw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209457-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209457
--- Comment #9 from Robert M. Muncrief (rmuncrief@humanavance.com) ---
The same type of problem also occurred when I had my old R9-390 and GT 710
GPUs, FX-6300 CPU, and Gigabyte GA-990FXA-UD5 motherboard. However if I put the
GT 710 in the primary PCIE slot the resume problem never occurred.
I can't be certain it was the exact same problem though, because there were a
lot of AMDGPU resume problems and I just assumed it was because the hardware I
had was so old. And since my R9 390 AMDGPU support was considered experimental
I figured I had to live with the issue.
So I really hoped it would go away when I got my two new RX 580 GPUs, R7 3700X
CPU, and X570 motherboard, but unfortunately the resume problem still occurs.
And I gave away my GT 710 so I can't check to see if it still alleviates the
issue.
--
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:[~2020-10-14 21:08 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 17:15 [Bug 209457] New: AMDGPU resume fail with RX 580 GPU bugzilla-daemon
2020-10-01 17:56 ` [Bug 209457] " bugzilla-daemon
2020-10-01 18:36 ` bugzilla-daemon
2020-10-01 18:56 ` bugzilla-daemon
2020-10-01 19:36 ` bugzilla-daemon
2020-10-02 1:25 ` bugzilla-daemon
2020-10-02 1:26 ` bugzilla-daemon
2020-10-14 20:07 ` bugzilla-daemon
2020-10-14 20:36 ` bugzilla-daemon
2020-10-14 21:08 ` bugzilla-daemon [this message]
2020-10-15 22:54 ` bugzilla-daemon
2020-10-29 23:11 ` bugzilla-daemon
2020-10-29 23:35 ` bugzilla-daemon
2020-10-29 23:41 ` bugzilla-daemon
2020-10-30 0:09 ` bugzilla-daemon
2020-11-11 16:51 ` bugzilla-daemon
2020-11-11 16:53 ` bugzilla-daemon
2020-11-11 16:54 ` bugzilla-daemon
2020-12-12 10:43 ` bugzilla-daemon
2020-12-12 11:21 ` bugzilla-daemon
2020-12-23 18:15 ` bugzilla-daemon
2021-03-05 14:35 ` bugzilla-daemon
2021-03-05 15:34 ` bugzilla-daemon
2021-05-15 17:48 ` bugzilla-daemon
2021-06-01 17:51 ` bugzilla-daemon
2021-06-01 20:21 ` bugzilla-daemon
2021-06-15 22:08 ` bugzilla-daemon
2021-06-16 20:57 ` bugzilla-daemon
2021-06-16 20:58 ` bugzilla-daemon
2021-06-18 18:22 ` bugzilla-daemon
2021-06-22 17:16 ` bugzilla-daemon
2021-06-30 19:01 ` bugzilla-daemon
2021-07-05 16:56 ` bugzilla-daemon
2021-07-06 13:44 ` bugzilla-daemon
2021-07-06 17:31 ` bugzilla-daemon
2021-07-14 14:51 ` bugzilla-daemon
2021-07-14 14:54 ` bugzilla-daemon
2021-07-14 14:55 ` bugzilla-daemon
2021-07-14 17:56 ` bugzilla-daemon
2021-07-14 18:43 ` bugzilla-daemon
2021-07-15 13:35 ` 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-209457-2300-LfN1fjB1jw@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.