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, 29 Jun 2021 16:06:04 -0400	[thread overview]
Message-ID: <CADnq5_NvNYpmGJQhQCi4uQPu54Qy4yvXrLiMMZW=WZeJG3XEBw@mail.gmail.com> (raw)
In-Reply-To: <CAB3xKZ1PQeZXiXNootYrdPc5RHo9KZ5vM8zX3V5ydAD8-AhfMA@mail.gmail.com>

On Tue, Jun 29, 2021 at 3:57 PM Ketsui <esgwpl@gmail.com> wrote:
>
> I have the 3200G I'm still getting this error with that version.

I think the 3200G may be a raven or raven2 variant rather than
picasso.  Can you try the latest firmware from upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/amdgpu

Alex

>
> [ +23.754701] amdgpu 0000:08:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:2 pasid:32773, for process mpv pid 5016 thread mpv:cs0 pid 5064)
> [  +0.000017] amdgpu 0000:08:00.0: amdgpu:   in page starting at address 0x80010009e000 from client 27
> [  +0.000007] amdgpu 0000:08:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00240C51
> [  +0.000003] amdgpu 0000:08:00.0: amdgpu:       Faulty UTCL2 client ID: CPG (0x6)
> [  +0.000003] amdgpu 0000:08:00.0: amdgpu:       MORE_FAULTS: 0x1
> [  +0.000002] amdgpu 0000:08:00.0: amdgpu:       WALKER_ERROR: 0x0
> [  +0.000002] amdgpu 0000:08:00.0: amdgpu:       PERMISSION_FAULTS: 0x5
> [  +0.000002] amdgpu 0000:08:00.0: amdgpu:       MAPPING_ERROR: 0x0
> [  +0.000001] amdgpu 0000:08:00.0: amdgpu:       RW: 0x1
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  reply	other threads:[~2021-06-29 20:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 15:45 AMDGPU error: "[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!" Ketsui
2021-06-29 20:06 ` Alex Deucher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-01 11:11 Ketsui
2021-06-30 10:04 Ketsui
2021-07-01  4:39 ` Alex Deucher
2021-06-30  4:18 Ketsui
2021-06-30  4:48 ` Alex Deucher
2021-06-01  2:29 Ketsui
2021-05-17  9:33 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
2021-07-15  1:42                           ` Ketsui
2021-07-15 17:07                       ` Michel Dänzer

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_NvNYpmGJQhQCi4uQPu54Qy4yvXrLiMMZW=WZeJG3XEBw@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.