All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Matthew Macy <mmacy@nextbsd.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: Looking for pointers on diagnosing ring test failure in amdgpu
Date: Mon, 13 Jun 2016 10:35:34 +0200	[thread overview]
Message-ID: <575E7056.8050606@amd.com> (raw)
In-Reply-To: <1554765fe53.c7ffcc09309539.98277193050942672@nextbsd.org>

Hi Matthew,

sounds like the UVD block doesn't want to initialize. No idea off hand 
why, could be anything. I would need the hardware here for a closer 
inspection.

For a workaround you can try to disable the UVD blokc using the 
ip_block_mask module parameter (it's a bitmask of enabled blocks e.g. 
0xffffffff means all blocks enabled, UVD is bit 7 on Carrizo IIRC).

Regards,
Christian.

Am 13.06.2016 um 03:35 schrieb Matthew Macy:
>
> I'm trying to bring up amdgpu an Carrizo A10 (Thinkpad e565 in case it matters) on FreeBSD. The driver is essentially unmodified from what is found in Linux 4.6 - relying on an extended version of FreeBSD's linuxkpi shims. The shims work well enough that i915/drm from 4.6 works extremely well on most hardware (I have yet to diagnose / fix the severe artifacts on Cherry Trail and Atom).
>
> On my A10 ring 11 test is failing:
>    https://gist.github.com/mattmacy/8e4a85072648eceb2445ad227dcc447c
>
> On my friend's A12 based EliteBook ring initialization succeeds:
> https://gist.github.com/mattmacy/d1fac64ab5190bb2568d6480dfbd7ee6
>
> With minor timing perturbations ring tests  will fail as early as ring 0.
>
> I'm hoping that one of the amdgpu developers might give me pointers on how to diagnose further and or what bugs in the linuxkpi might be causing this. I know that I can selectively disable the rings, but that doesn't help fix the underlying problem.
>
> Thanks in advance.
>
> -M
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-06-13  8:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13  1:35 Looking for pointers on diagnosing ring test failure in amdgpu Matthew Macy
2016-06-13  8:35 ` Christian König [this message]
2016-06-13 22:03   ` Matthew Macy
2016-06-14  8:10     ` Christian König
2016-06-14 13:02       ` Alex Deucher
2016-06-14 20:02         ` Matthew Macy
2016-06-14 20:08           ` Matthew Macy
2016-06-14 20:10           ` Deucher, Alexander

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=575E7056.8050606@amd.com \
    --to=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=mmacy@nextbsd.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.