All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Morell <rmorell-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
Cc: "nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	gpu-public-documentation
	<gpu-public-documentation-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: Documentation request for MP warp error 0x10
Date: Fri, 2 Oct 2015 14:48:11 -0700	[thread overview]
Message-ID: <20151002214811.GD9436@morell.nvidia.com> (raw)
In-Reply-To: <CAKb7Uvhwd8VSDya3EZ2o2VsvnBudTBTMWDbJvSE9mnBi7ybX3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Ilia,

Error 0x10 is INVALID_ADDR_SPACE. It is triggered when an ATOM or RED [1]
instruction accesses local or shared memory. Global memory accesses are the
only allowed accesses for ATOM and RED instructions.


Note that SM30 also has this restriction that ATOM and RED should only be used
on global memory, but it is not error-checked in hardware until SM35.


[1] What is documented as RED internally appears to be called SUREDP in Mesa.


- Robert

On Wed, Sep 30, 2015 at 03:14:47PM -0400, Ilia Mirkin wrote:
> Hello,
> 
> I've recently come across an error reported by the GPU and would like
> to know what it means and especially what causes it to be triggered.
> Any information would be very useful:
> 
> I'm seeing MP warp error 0x10 (appears in MP register 0x48). This is
> what we currently have in nouveau:
> 
> <reg32 offset="0x048" name="TRAP_WARP_ERROR"> <!-- ctx-switched -->
> <bitfield high="15" low="0" name="ID">
> <value value="1" name="STACK_MISMATCH"/>
> <value value="5" name="MISALIGNED_PC"/>
> <value value="8" name="MISALIGNED_GPR"/>
> <value value="9" name="INVALID_OPCODE"/>
> <value value="13" name="GPR_OUT_OF_BOUNDS"/>
> <value value="14" name="MEM_OUT_OF_BOUNDS"/>
> <value value="17" name="INVALID_PARAM"/>
> </bitfield>
> </reg32>
> 
> [Additionally it seems like 15 = UNALIGNED_MEM_ACCESS]
> 
> It seems to happen whenever I try to access global memory on kepler
> (potentially only atomics, not sure at this point). Knowing precisely
> what causes the error to get triggered (and esp what we need to do in
> order not to trigger it) would be most useful.
> 
> For reference, my shader looks something like this (for SM35):
> 
>         /*0018*/                   LDC.64 R0, c[0xf][0x1c0];
>   /* 0x7ca80780e01ffc02 */
>         /*0020*/                   ATOM.E.ADD R2, [R0], R2;
>   /* 0x68080000011c000a */
>         /*0028*/                   LD.E.CG R0, [R0];
>   /* 0xcc800000001c0000 */
> 
> I know that the proprietary drivers are a lot more sophisticated and
> only do the atomic add from a single lane, but I was assuming that was
> not required.
> 
> Thanks,
> 
>   -ilia
> 
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2015-10-02 21:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 19:14 Documentation request for MP warp error 0x10 Ilia Mirkin
     [not found] ` <CAKb7Uvhwd8VSDya3EZ2o2VsvnBudTBTMWDbJvSE9mnBi7ybX3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-02 21:48   ` Robert Morell [this message]
     [not found]     ` <20151002214811.GD9436-f3YH7lVHJt/FT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2015-10-02 22:05       ` Ilia Mirkin
     [not found]         ` <CAKb7Uvi6se5YExUuJ8SShfuQD9Gy2QQF1N31k_3Q11roMHa=4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-02 22:14           ` Robert Morell
     [not found]             ` <20151002221456.GE9436-f3YH7lVHJt/FT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2015-10-26 19:28               ` Ilia Mirkin
     [not found]                 ` <CAKb7Uvjpmxn8kR3DhbXSh0SXmsGCQ-+dP1iQX7j30QiGFtbStg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-26 20:02                   ` Robert Morell
     [not found]                     ` <20151026200256.GB7638-f3YH7lVHJt/FT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2015-11-06 20:59                       ` Robert Morell
     [not found]                         ` <20151106205932.GA6669-f3YH7lVHJt/FT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2015-11-06 21:15                           ` Ilia Mirkin
     [not found]                             ` <CAKb7UviaiH-twaJr9tngGvwkBn1W+PujppSES+GYRLxVr3nvvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-11-06 21:19                               ` Robert Morell
     [not found]                                 ` <20151106211951.GC6669-f3YH7lVHJt/FT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2015-11-07  0:55                                   ` Ilia Mirkin

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=20151002214811.GD9436@morell.nvidia.com \
    --to=rmorell-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
    --cc=gpu-public-documentation-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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.