From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 213391] AMDGPU retries page fault with some specific processes amdgpu and sometimes followed [gfxhub0] retry page fault until *ERROR* ring gfx timeout, but soft recovered
Date: Fri, 10 Sep 2021 13:29:28 +0000 [thread overview]
Message-ID: <bug-213391-2300-1CTzyFsHUL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213391-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213391
--- Comment #37 from Michel Dänzer (michel@daenzer.net) ---
(In reply to Lahfa Samy from comment #36)
> Did anyone test whether this has been fixed in newer firmware updates, or
> should we still stay on version 20210315.3568f96-3 ?
It's fixed in upstream linux-firmware 20210818.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-09-10 13:29 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 11:16 [Bug 213391] New: AMDGPU retries page fault with some specific processes amdgpu: [gfxhub0] retry page fault until *ERROR* ring gfx timeout, but soft recovered bugzilla-daemon
2021-06-10 11:33 ` [Bug 213391] " bugzilla-daemon
2021-06-10 11:43 ` bugzilla-daemon
2021-06-10 12:34 ` [Bug 213391] AMDGPU retries page fault with some specific processes amdgpu and sometimes " bugzilla-daemon
2021-06-10 12:34 ` [Bug 213391] AMDGPU retries page fault with some specific processes amdgpu and sometimes followed " bugzilla-daemon
2021-06-10 12:36 ` bugzilla-daemon
2021-06-10 12:51 ` bugzilla-daemon
2021-06-10 13:09 ` bugzilla-daemon
2021-06-10 13:19 ` bugzilla-daemon
2021-06-10 17:41 ` bugzilla-daemon
2021-06-10 19:45 ` bugzilla-daemon
2021-06-11 7:31 ` bugzilla-daemon
2021-06-11 23:32 ` bugzilla-daemon
2021-06-12 23:02 ` bugzilla-daemon
2021-06-13 17:43 ` bugzilla-daemon
2021-06-14 8:01 ` bugzilla-daemon
2021-06-15 22:14 ` bugzilla-daemon
2021-06-16 8:51 ` bugzilla-daemon
2021-06-16 10:46 ` bugzilla-daemon
2021-06-16 20:55 ` bugzilla-daemon
2021-06-18 18:27 ` bugzilla-daemon
2021-06-18 20:30 ` bugzilla-daemon
2021-06-19 12:15 ` bugzilla-daemon
2021-06-20 13:02 ` bugzilla-daemon
2021-06-20 21:07 ` bugzilla-daemon
2021-06-21 7:04 ` bugzilla-daemon
2021-06-21 18:55 ` bugzilla-daemon
2021-06-21 19:26 ` bugzilla-daemon
2021-06-29 23:55 ` bugzilla-daemon
2021-06-29 23:58 ` bugzilla-daemon
2021-06-30 19:00 ` bugzilla-daemon
2021-07-05 16:55 ` bugzilla-daemon
2021-07-06 17:35 ` bugzilla-daemon
2021-07-08 18:24 ` bugzilla-daemon
2021-07-08 18:28 ` bugzilla-daemon
2021-07-15 13:29 ` bugzilla-daemon
2021-07-15 13:31 ` bugzilla-daemon
2021-08-14 21:00 ` bugzilla-daemon
2021-09-10 11:46 ` bugzilla-daemon
2021-09-10 13:29 ` bugzilla-daemon [this message]
2021-11-19 13:28 ` 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-213391-2300-1CTzyFsHUL@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;
as well as URLs for NNTP newsgroup(s).