From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205675] Display locks up. AMDGPU timeout
Date: Wed, 27 Nov 2019 14:56:38 +0000 [thread overview]
Message-ID: <bug-205675-2300-OSoxWGw2jl@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205675-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205675
Pierre-Eric Pelloux-Prayer (pierre-eric.pelloux-prayer@amd.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pierre-eric.pelloux-prayer@
| |amd.com
--- Comment #1 from Pierre-Eric Pelloux-Prayer (pierre-eric.pelloux-prayer@amd.com) ---
Thanks for the bug report.
The sdma0 timeout issue (from you dmesg) has already been reported. The most
active bug report is: https://gitlab.freedesktop.org/drm/amd/issues/892
Note that sdma usage for Navi is disabled for Mesa 19.3 and 19.2.5 so this
issue shouldn't occur if you use one of these releases.
Other related issues:
- https://bugzilla.kernel.org/show_bug.cgi?id=205169 - has a patch but need to
be applied manually until it makes it to an upstream release
- gfx timeout issues: those are likely to be game specific and are probably a
bug in Mesa (https://gitlab.freedesktop.org/mesa/mesa/issues)
--
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:[~2019-11-27 14:56 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 3:47 [Bug 205675] New: Display locks up. AMDGPU timeout bugzilla-daemon
2019-11-27 14:56 ` bugzilla-daemon [this message]
2019-11-27 18:17 ` [Bug 205675] " bugzilla-daemon
2020-02-09 15:33 ` bugzilla-daemon
2020-02-09 15:34 ` bugzilla-daemon
2020-02-09 17:23 ` bugzilla-daemon
2020-11-21 18:51 ` bugzilla-daemon
2020-11-21 19:32 ` bugzilla-daemon
2020-11-21 19:45 ` bugzilla-daemon
2020-11-21 20:24 ` bugzilla-daemon
2020-11-21 20:58 ` bugzilla-daemon
2020-11-21 21:10 ` bugzilla-daemon
2020-11-21 22:31 ` bugzilla-daemon
2020-11-21 23:19 ` bugzilla-daemon
2020-11-22 0:10 ` bugzilla-daemon
2020-11-22 1:01 ` bugzilla-daemon
2020-11-22 1:12 ` bugzilla-daemon
2020-11-22 1:53 ` bugzilla-daemon
2020-11-22 2:10 ` bugzilla-daemon
2020-11-22 3:14 ` bugzilla-daemon
2020-11-22 3:29 ` bugzilla-daemon
2020-11-22 4:11 ` bugzilla-daemon
2020-11-22 13:56 ` bugzilla-daemon
2020-11-22 14:59 ` bugzilla-daemon
2020-11-22 15:32 ` bugzilla-daemon
2020-11-22 15:55 ` bugzilla-daemon
2020-11-22 16:47 ` bugzilla-daemon
2020-11-22 17:22 ` bugzilla-daemon
2020-11-22 18:12 ` bugzilla-daemon
2020-11-22 18:48 ` bugzilla-daemon
2020-11-22 19:47 ` bugzilla-daemon
2020-11-22 20:39 ` bugzilla-daemon
2020-11-22 21:01 ` bugzilla-daemon
2020-11-22 23:10 ` bugzilla-daemon
2020-11-22 23:49 ` bugzilla-daemon
2020-11-23 0:19 ` bugzilla-daemon
2020-11-23 1:09 ` bugzilla-daemon
2020-11-23 1:18 ` bugzilla-daemon
2020-11-24 15:07 ` bugzilla-daemon
2020-11-24 15:43 ` bugzilla-daemon
2020-11-24 17:41 ` bugzilla-daemon
2020-11-25 16:47 ` bugzilla-daemon
2020-11-25 17:39 ` bugzilla-daemon
2020-12-21 23:50 ` bugzilla-daemon
2020-12-22 1:05 ` bugzilla-daemon
2021-01-03 16:49 ` 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-205675-2300-OSoxWGw2jl@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