dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 213145] AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!"
Date: Sun, 09 Oct 2022 20:11:53 +0000	[thread overview]
Message-ID: <bug-213145-2300-TXQ042hH1k@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213145-2300@https.bugzilla.kernel.org/>

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

James Le Cuirot (chewi@gentoo.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chewi@gentoo.org

--- Comment #23 from James Le Cuirot (chewi@gentoo.org) ---
Same. I see this quite frequently with my RX 6800 XT, particularly when using
Vivaldi, though that may just be a coincidence, since I use it a lot.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-10-09 20:11 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 14:46 [Bug 213145] New: AMDGPU resets, timesout and crashes after "*ERROR* Waiting for fences timed out!" bugzilla-daemon
2021-05-19 14:47 ` [Bug 213145] " bugzilla-daemon
2021-05-19 14:47 ` bugzilla-daemon
2021-05-27 13:43 ` bugzilla-daemon
2021-06-04 21:37 ` bugzilla-daemon
2021-06-04 21:38 ` bugzilla-daemon
2021-06-05  0:38 ` bugzilla-daemon
2021-06-07 19:37 ` bugzilla-daemon
2021-06-07 19:41 ` bugzilla-daemon
2021-06-08 16:38 ` bugzilla-daemon
2021-06-08 17:17 ` bugzilla-daemon
2021-06-08 17:25 ` bugzilla-daemon
2021-06-08 17:30 ` bugzilla-daemon
2022-05-25  2:21 ` bugzilla-daemon
2022-05-25  2:30 ` bugzilla-daemon
2022-05-25  4:03 ` bugzilla-daemon
2022-05-25  4:07 ` bugzilla-daemon
2022-05-25 20:18 ` bugzilla-daemon
2022-05-29  7:40 ` bugzilla-daemon
2022-05-31 19:59 ` bugzilla-daemon
2022-06-13  6:58 ` bugzilla-daemon
2022-07-26 20:42 ` bugzilla-daemon
2022-09-12 17:07 ` bugzilla-daemon
2022-09-30 15:00 ` bugzilla-daemon
2022-10-09 20:11 ` bugzilla-daemon [this message]
2022-10-10 18:24 ` bugzilla-daemon
2022-10-12 10:51 ` bugzilla-daemon
2022-10-12 12:01 ` bugzilla-daemon
2022-10-30 16:57 ` bugzilla-daemon
2022-11-12 16:24 ` bugzilla-daemon
2022-11-20 21:57 ` bugzilla-daemon
2022-11-26 20:19 ` bugzilla-daemon
2023-07-01  5:25 ` bugzilla-daemon
2023-07-01  5:27 ` bugzilla-daemon
2024-01-04 11:33 ` bugzilla-daemon
2024-02-04  0:04 ` 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-213145-2300-TXQ042hH1k@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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).