dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206141] VCE UVD ring test failed -110
Date: Fri, 17 Jan 2020 21:16:45 +0000	[thread overview]
Message-ID: <bug-206141-2300-iIfZqeJnVy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206141-2300@https.bugzilla.kernel.org/>

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

--- Comment #8 from Alex Deucher (alexdeucher@gmail.com) ---
(In reply to Janpieter Sollie from comment #7)
> Is it possible to disable the UVD/VCE engine on the original GPU?
> I mean, it's not used anyway, so I might as well disable it completely to
> avoid these errors.

Yes.  Set the amdgpu.ip_block_mask module parameter on the kernel command line
in grub.  Each bit refers to an IP.  From your log:

[    3.987749] [drm] add ip block number 0 <vi_common>
[    3.987750] [drm] add ip block number 1 <gmc_v8_0>
[    3.987751] [drm] add ip block number 2 <tonga_ih>
[    3.987752] [drm] add ip block number 3 <gfx_v8_0>
[    3.987753] [drm] add ip block number 4 <sdma_v3_0>
[    3.987753] [drm] add ip block number 5 <powerplay>
[    3.987754] [drm] add ip block number 6 <dm>
[    3.987755] [drm] add ip block number 7 <uvd_v6_0>
[    3.987755] [drm] add ip block number 8 <vce_v3_0>

bits 7 and 8 are for uvd and vce, so you can append amdgpu.ip_block_mask=0x7f
to only enable blocks 0-6.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-01-17 21:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09  9:18 [Bug 206141] New: VCE UVD ring test failed -110 bugzilla-daemon
2020-01-11 22:02 ` [Bug 206141] " bugzilla-daemon
2020-01-11 22:03 ` bugzilla-daemon
2020-01-13 13:08 ` bugzilla-daemon
2020-01-13 16:39 ` bugzilla-daemon
2020-01-14  6:23 ` bugzilla-daemon
2020-01-14 19:27 ` bugzilla-daemon
2020-01-14 19:50 ` bugzilla-daemon
2020-01-17 16:34 ` bugzilla-daemon
2020-01-17 21:16 ` bugzilla-daemon [this message]
2020-01-18  6:40 ` 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-206141-2300-iIfZqeJnVy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).