All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: "Marek Olšák" <maraeo@gmail.com>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Radeon R700 multi-ring bug
Date: Sat, 19 Apr 2014 11:54:13 +0200	[thread overview]
Message-ID: <535247C5.1020601@vodafone.de> (raw)
In-Reply-To: <CAAxE2A51R6d3Y8BSqCVzUxKRXuZNNT-+YMADH1NR1+CNq2OJ8w@mail.gmail.com>

Hi Marek,

I've noticed this before as well, and I agree that it looks like a 
memory corruption. Not sure if the async DMA on the GPU or the CPU is 
overwriting something because of a race condition or something like this.

Anyway, can you come up with a simple test case to reproduce the issue? 
For me it occurred only randomly while working on UVD support for R7xx. 
If you have something more reliable I could dig into it with my RV710.

Christian.

Am 19.04.2014 01:48, schrieb Marek Olšák:
> Hi,
>
> If you submit a lot of graphics and DMA IBs interleaved, the graphics
> CS checker sometimes fails with this message:
>
> [ 3846.435661] Forbidden register 0x0014 in cs at 9
> [ 3846.435664] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
>
> This error is only used for type-0 packets, but we don't use these
> packets on R700 at all. Somehow, the graphics CS checker received
> either the DMA IB or random garbage. My guess is there is memory
> corruption happening during IB uploading and/or IB checking in the
> kernel. Also, if you are unlucky, the GPU hangs instead.
>
> The CS thread offloading was disabled in Mesa, so the user space was
> single-threaded.
>
> There are 2 ways to fix this:
> - disable async DMA in Mesa
> - call usleep(1) after the RADEON_CS ioctl returns
>
> This is just a heads-up. In the worst case, we can disable async DMA
> for R700 in Mesa.
>
> Marek
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2014-04-19  9:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-18 23:48 Radeon R700 multi-ring bug Marek Olšák
2014-04-19  9:54 ` Christian König [this message]
2014-04-19 14:43   ` Alex Deucher
2014-04-19 15:07   ` Marek Olšák
2014-04-19 15:19     ` Alex Deucher
2014-04-19 16:09       ` Marek Olšák

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=535247C5.1020601@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=maraeo@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.