All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 16 Jun 2021 08:51:31 +0000	[thread overview]
Message-ID: <bug-213391-2300-YR1tkDzm1c@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 #15 from Michel Dänzer (michel@daenzer.net) ---
(In reply to Dominic Letz from comment #14)
> Having the same issue on an E495 with Kernel 5.12.9. Will try to downgrade
> the /lib/firmware/amdgpu any hint to which git tag you would consider safe?

20210315 seems to work fine here (on an E595).

-- 
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:[~2021-06-16  8:51 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 [this message]
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
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-YR1tkDzm1c@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.