All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: Ketsui <esgwpl@gmail.com>
Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: AMDGPU error: "[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!"
Date: Tue, 13 Jul 2021 10:40:30 -0400	[thread overview]
Message-ID: <CADnq5_OLvV9LoNTFsiCi_Cm1-zYZmRyLvyCK59Kn7rZzrndXPA@mail.gmail.com> (raw)
In-Reply-To: <YOqiQmAUTBWjbVb6@mainframe.localdomain>

On Mon, Jul 12, 2021 at 3:18 AM Ketsui <esgwpl@gmail.com> wrote:
>
> > So far, so good; no hang in a week. I'll try the rest of the new firmware as well now, will follow up if there's a hang again.
>
> I've noticed that the VM_L2_PROTECTION_FAULT_STATUS error doesn't always result in a hang, looking through my journal I can see
> maybe a dozen of them spread out across multiple boots but my system only became non-functional like two times so far (I know
> because I have the dmesg when the hangs happened saved, you can find them attached to this mail).
>
> To make myself clear, I haven't actually had a hang too with the new firmwares even though these messages still appear on my dmesg,
> sorry if my feedback gave the wrong impression.

Were these issues mitigated with older firmware for you previously?

Alex
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2021-07-13 14:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17  9:33 AMDGPU error: "[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!" xgqt
2021-05-18 14:10 ` Michel Dänzer
2021-05-18 22:05   ` Alex Deucher
2021-05-19  8:48     ` Michel Dänzer
2021-05-19 13:57       ` Alex Deucher
2021-06-04  7:47         ` Michel Dänzer
2021-06-04 12:33           ` Alex Deucher
2021-06-04 13:08             ` Michel Dänzer
2021-06-24 10:51               ` Michel Dänzer
2021-06-28 17:16                 ` Deucher, Alexander
2021-06-29 10:36                   ` Michel Dänzer
2021-07-08 16:13                     ` Michel Dänzer
2021-07-11  7:48                       ` Ketsui
2021-07-12  8:36                         ` Michel Dänzer
2021-07-13 14:40                         ` Alex Deucher [this message]
2021-07-15  1:42                           ` Ketsui
2021-07-15 17:07                       ` Michel Dänzer
2021-06-01  2:29 Ketsui
2021-06-29 15:45 Ketsui
2021-06-29 20:06 ` Alex Deucher
2021-06-30  4:18 Ketsui
2021-06-30  4:48 ` Alex Deucher
2021-06-30 10:04 Ketsui
2021-07-01  4:39 ` Alex Deucher
2021-07-01 11:11 Ketsui

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=CADnq5_OLvV9LoNTFsiCi_Cm1-zYZmRyLvyCK59Kn7rZzrndXPA@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=esgwpl@gmail.com \
    /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.