From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204987] fault in amdgpu_dm_atomic_commit_tail on Vega64 with compton and redshift
Date: Mon, 07 Sep 2020 10:42:48 +0000 [thread overview]
Message-ID: <bug-204987-2300-MpWylcZqhs@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204987-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204987
Bhasker C V (bhasker@unixindia.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bhasker@unixindia.com
--- Comment #3 from Bhasker C V (bhasker@unixindia.com) ---
I get this error after hibernation and resume. This does not happen during
immediate resume but if left overnight and resume in the morning, I see the
amdgpu_dm_atomic_commit_tail.
I am failing to load kexec kernel when on AMD ryzen. Hence I have a shapshot of
the error message. The system freezes and there is nothing that can be done
other than to cold reboot.
Attaching a photo of the crash
--
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-09-07 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 20:18 [Bug 204987] New: general protection fault in amdgpu_dm_atomic_commit_tail (Vega64) bugzilla-daemon
2019-09-24 20:19 ` [Bug 204987] " bugzilla-daemon
2019-09-26 8:22 ` bugzilla-daemon
2019-12-13 23:58 ` [Bug 204987] fault in amdgpu_dm_atomic_commit_tail on Vega64 with compton and redshift bugzilla-daemon
2019-12-14 0:00 ` bugzilla-daemon
2020-09-07 10:42 ` bugzilla-daemon [this message]
2020-09-07 10:44 ` bugzilla-daemon
2021-11-02 17: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-204987-2300-MpWylcZqhs@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.