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 18:17:59 +0000 [thread overview]
Message-ID: <bug-205675-2300-ixEEzGowgM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205675-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205675
--- Comment #2 from freddyreimer@comcast.net ---
Hello! Glad to see there's others looking at this. My mesa is on 19.3.0_rc4,
but the issue is still happening. That related bug in your second link talks
about 5.4 kernel being out but not having the fix. Is this something that might
show up in 5.4.1?
I might try going to mesa 19.2.5 or 19.2.6 specifically later though, in case
the mesa-side disable isn't in rc4 for some reason. Seems like it might be a
kernel issue though.
--
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 18:17 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 ` [Bug 205675] " bugzilla-daemon
2019-11-27 18:17 ` bugzilla-daemon [this message]
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-ixEEzGowgM@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.