All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204241] amdgpu fails to resume from suspend
Date: Sun, 17 May 2020 20:40:35 +0000	[thread overview]
Message-ID: <bug-204241-2300-qTIID71Qpc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204241-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=204241

igor@sonce.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |igor@sonce.de

--- Comment #61 from igor@sonce.de ---
(In reply to Ulf Winkelvos from comment #50)
> I tried to bisect this issue in the past days, but it is almost impossible
> to track it down, as it is so hard to reproduce it reliably. It seems that
> 5.2 is "better", the close the commits go to 5.3 it gets "worse". Now all of
> a sudden 5.4.3-arch1-1 is completely stable so far... I am going to create a
> new bug, whenever this comes back.

Thank you,
You saved my day. Switched from 5.4.0 to 5.4.3 and now I am able to properly
suspend and resume.
With 5.4.0 the system crashed and reset.

keep save and healthy.
By
Igor

-- 
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-05-17 20:40 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-20  9:50 [Bug 204241] New: amdgpu fails to resume from suspend bugzilla-daemon
2019-07-20  9:50 ` [Bug 204241] " bugzilla-daemon
2019-08-08 20:13 ` bugzilla-daemon
2019-08-08 20:22 ` bugzilla-daemon
2019-08-08 21:02 ` bugzilla-daemon
2019-08-14 19:29 ` bugzilla-daemon
2019-08-14 19:38 ` bugzilla-daemon
2019-08-14 19:39 ` bugzilla-daemon
2019-08-14 19:39 ` bugzilla-daemon
2019-08-14 21:04 ` bugzilla-daemon
2019-08-15 20:55 ` bugzilla-daemon
2019-08-19 13:35 ` bugzilla-daemon
2019-09-03 18:56 ` bugzilla-daemon
2019-09-21 18:31 ` bugzilla-daemon
2019-10-05  0:08 ` bugzilla-daemon
2019-10-05 10:35 ` bugzilla-daemon
2019-10-07 10:13 ` bugzilla-daemon
2019-10-07 18:10 ` bugzilla-daemon
2019-10-08  7:56 ` bugzilla-daemon
2019-10-08  9:40 ` bugzilla-daemon
2019-10-11 18:33 ` bugzilla-daemon
2019-10-11 18:37 ` bugzilla-daemon
2019-10-11 20:47 ` bugzilla-daemon
2019-10-11 20:48 ` bugzilla-daemon
2019-10-12 10:37 ` bugzilla-daemon
2019-10-12 16:25 ` bugzilla-daemon
2019-10-12 18:35 ` bugzilla-daemon
2019-10-12 20:47 ` bugzilla-daemon
2019-10-13 10:47 ` bugzilla-daemon
2019-10-15 22:11 ` bugzilla-daemon
2019-10-15 22:12 ` bugzilla-daemon
2019-10-15 22:12 ` bugzilla-daemon
2019-10-16 14:27 ` bugzilla-daemon
2019-10-16 14:29 ` bugzilla-daemon
2019-10-16 17:29 ` bugzilla-daemon
2019-10-16 22:03 ` bugzilla-daemon
2019-10-20 20:06 ` bugzilla-daemon
2019-10-23 16:46 ` bugzilla-daemon
2019-10-28 20:16 ` bugzilla-daemon
2019-11-30 18:24 ` bugzilla-daemon
2019-12-07 10:28 ` bugzilla-daemon
2019-12-07 23:50 ` bugzilla-daemon
2019-12-07 23:55 ` bugzilla-daemon
2019-12-11  0:37 ` bugzilla-daemon
2019-12-11  0:39 ` bugzilla-daemon
2019-12-12  5:00 ` bugzilla-daemon
2019-12-12 14:37 ` bugzilla-daemon
2019-12-13 10:38 ` bugzilla-daemon
2019-12-16  4:40 ` bugzilla-daemon
2019-12-16 13:40 ` bugzilla-daemon
2019-12-20 22:17 ` bugzilla-daemon
2020-02-25  1:22 ` bugzilla-daemon
2020-02-25  2:00 ` bugzilla-daemon
2020-02-25  3:06 ` bugzilla-daemon
2020-02-25 17:26 ` bugzilla-daemon
2020-02-25 21:26 ` bugzilla-daemon
2020-02-26  9:54 ` bugzilla-daemon
2020-04-10 21:16 ` bugzilla-daemon
2020-04-15 19:43 ` bugzilla-daemon
2020-04-15 19:50 ` bugzilla-daemon
2020-05-13 20:45 ` bugzilla-daemon
2020-05-17 20:40 ` bugzilla-daemon [this message]
2020-06-24 19:15 ` bugzilla-daemon
2020-07-27 16:02 ` bugzilla-daemon
2020-07-27 16:03 ` bugzilla-daemon
2020-09-25  7:31 ` bugzilla-daemon
2020-09-25  7:34 ` bugzilla-daemon
2020-09-30  9:22 ` bugzilla-daemon
2020-09-30 16:31 ` bugzilla-daemon
2020-09-30 19:23 ` bugzilla-daemon
2020-09-30 20:03 ` bugzilla-daemon
2020-10-01 14:59 ` bugzilla-daemon
2020-10-01 17:21 ` bugzilla-daemon
2020-10-01 17:27 ` bugzilla-daemon
2020-10-01 17:55 ` bugzilla-daemon
2021-02-08 22:00 ` bugzilla-daemon
2021-02-08 22:13 ` bugzilla-daemon
2021-02-08 22:15 ` bugzilla-daemon
2023-04-13 20:11 ` bugzilla-daemon
2024-09-23  5:50 ` bugzilla-daemon
2024-09-24 21:50 ` 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-204241-2300-qTIID71Qpc@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.