dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209457] AMDGPU resume fail with RX 580 GPU
Date: Thu, 01 Oct 2020 18:36:05 +0000	[thread overview]
Message-ID: <bug-209457-2300-EYhXS5ex9y@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 #2 from Robert M. Muncrief (rmuncrief@humanavance.com) ---
Created attachment 292741
  --> https://bugzilla.kernel.org/attachment.cgi?id=292741&action=edit
Resume failure, full dmesg output from kernel 5.8.5

The last full dmesg output I have is from kernel 5.8.5, and I've attached it to
this response. However the messages haven't changed since then.  

Going forward would you rather I run the current 5.8 (on arch it's 5.8.12) or
the 5.9 RC release candidates (currently 5.9-rc6) to capture the next event?  

I can bisect, but don't know how to bisect a random issue like this. It's
difficult to say how often it happens, but I'd estimate one out of seven to
twelve times.  

I actually tried purposely going through multiple suspend/resume cycles
sometime ago in hopes of gathering more info for a bug report, but got to 20
cycles with no errors so I gave up. So it seems the issue only occurs if my
computer has been suspended for a significant period of time, as it only occurs
when my computer has been suspended overnight.  

It's also significant to note that I have two identical XFX Radeon RX 580 GTS
XXX Edition GPUs, and one is passed through via VFIO at boot.  

In any case I'll be happy to assist on this issue in any way I can. I've seen
multiple complaints about it online, but saw other bug reports that I assumed
were already addressing it or I would have filed a new bug report sooner. I
wasn't aware of my error until this morning.

-- 
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

  parent reply	other threads:[~2020-10-01 18:36 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 [this message]
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
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-EYhXS5ex9y@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 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).