All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Tom St Denis <tom.stdenis-5C7GfCeVMHo@public.gmane.org>,
	amd-gfx mailing list
	<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: error messages from running uvd on polaris10
Date: Mon, 29 Jan 2018 19:50:26 +0100	[thread overview]
Message-ID: <db8ebbbb-c678-d977-102c-ab3e782fda35@gmail.com> (raw)
In-Reply-To: <1fe2acde-4518-5bdd-0584-1c3e19aaa114-5C7GfCeVMHo@public.gmane.org>

Hi Tom,

well that is an interesting one. Looks like we use more dw on the UVD 
ring when prime is enabled.

Going to take a look tomorrow,
Christian

Am 29.01.2018 um 19:45 schrieb Tom St Denis:
> Hi all,
>
> Getting these:
>
> [  537.515830] [drm:uvd_v6_0_ring_emit_fence [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.516057] [drm:uvd_v6_0_ring_emit_fence [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.516267] [drm:uvd_v6_0_ring_emit_fence [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.516485] [drm:uvd_v6_0_ring_emit_fence [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.516823] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.517080] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.517323] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.517605] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.517848] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.518090] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.518330] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.518581] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.518807] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.519034] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.519260] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
> [  537.519486] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: 
> writing more dwords to the ring than expected!
>
>
> from running
>
> DRI_PRIME=1 mpv --hwdec=auto *mkv
>
> on my CZ+Polaris10 setup (with drm-next up to date).  I don't get the 
> messages though if I run without DRI_PRIME=1 and they both have the 
> same UVD6 right?
>
> Is it because one is in physical vs VM mode?
>
> Cheers,
> Tom
> _______________________________________________
> 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

  parent reply	other threads:[~2018-01-29 18:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 18:45 error messages from running uvd on polaris10 Tom St Denis
     [not found] ` <1fe2acde-4518-5bdd-0584-1c3e19aaa114-5C7GfCeVMHo@public.gmane.org>
2018-01-29 18:50   ` Christian König [this message]
     [not found]     ` <db8ebbbb-c678-d977-102c-ab3e782fda35-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-29 18:53       ` Tom St Denis
     [not found]         ` <d0149fb1-c220-cbfa-9935-c95a5b5cfd2a-5C7GfCeVMHo@public.gmane.org>
2018-01-30 14:16           ` Tom St Denis

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=db8ebbbb-c678-d977-102c-ab3e782fda35@gmail.com \
    --to=ckoenig.leichtzumerken-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=christian.koenig-5C7GfCeVMHo@public.gmane.org \
    --cc=tom.stdenis-5C7GfCeVMHo@public.gmane.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.