dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216143] [bisected] garbled screen when starting X + dmesg cluttered with "[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed in the dependencies handling -1431655766!"
Date: Sat, 02 Jul 2022 22:14:42 +0000	[thread overview]
Message-ID: <bug-216143-2300-YCi5ZzEzK1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216143-2300@https.bugzilla.kernel.org/>

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

--- Comment #7 from Erhard F. (erhard_f@mailbox.org) ---
(In reply to Alex Deucher from comment #5)
> Does this patch help?
> https://patchwork.freedesktop.org/patch/490475/
Had a closer look at the patch as it did not apply on top of v5.19-rc4. Seems
like almost all of the patch diff is already in upstream v5.19-rc4. Only thing
left to patch is:

--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c    2022-07-02 21:59:53.171528202
+0200
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c    2022-07-02 23:12:13.481985665
+0200
@@ -579,16 +579,6 @@ static int amdgpu_cs_parser_bos(struct a
                e->bo_va = amdgpu_vm_bo_find(vm, bo);
        }

-       /* Move fence waiting after getting reservation lock of
-        * PD root. Then there is no need on a ctx mutex lock.
-        */
-       r = amdgpu_ctx_wait_prev_fence(p->ctx, p->entity);
-       if (unlikely(r != 0)) {
-               if (r != -ERESTARTSYS)
-                       DRM_ERROR("amdgpu_ctx_wait_prev_fence failed.\n");
-               goto error_validate;
-       }
-
        amdgpu_cs_get_threshold_for_moves(p->adev, &p->bytes_moved_threshold,
                                          &p->bytes_moved_vis_threshold);
        p->bytes_moved = 0;
@@ -947,7 +937,7 @@ static int amdgpu_cs_ib_fill(struct amdg
        if (parser->job->uf_addr && ring->funcs->no_user_fence)
                return -EINVAL;

-       return 0;
+       return amdgpu_ctx_wait_prev_fence(parser->ctx, parser->entity);
 }

 static int amdgpu_cs_process_fence_dep(struct amdgpu_cs_parser *p,


But applying this on top of v5.19-rc4 does not help either. I still need to
revert 94f4c4965e5513ba624488f4b601d6b385635aec to get X going.

-- 
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-07-04 16:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 21:44 [Bug 216143] New: [bisected] garbled screen when starting X + dmesg cluttered with "[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed in the dependencies handling -1431655766!" bugzilla-daemon
2022-06-17 21:45 ` [Bug 216143] " bugzilla-daemon
2022-06-17 21:45 ` bugzilla-daemon
2022-06-17 21:45 ` bugzilla-daemon
2022-06-17 22:08 ` bugzilla-daemon
2022-06-27 21:31 ` bugzilla-daemon
2022-06-28  0:04 ` bugzilla-daemon
2022-07-02 22:14 ` bugzilla-daemon [this message]
2022-07-10 11:02 ` bugzilla-daemon
2022-07-18 23:59 ` bugzilla-daemon
2022-08-15 14:09 ` bugzilla-daemon
2022-08-15 14:10 ` bugzilla-daemon
2022-08-27 13:46 ` bugzilla-daemon
2022-08-27 13:51 ` bugzilla-daemon
2022-08-27 13:56 ` bugzilla-daemon
2022-08-27 14:22 ` bugzilla-daemon
2022-11-14 22:58 ` bugzilla-daemon
2022-11-14 23:00 ` bugzilla-daemon
2023-02-16 23:21 ` 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-216143-2300-YCi5ZzEzK1@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