From: Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ben Skeggs <skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/nv50: decode PGRAPH status registers on TLB flush fail
Date: Wed, 7 Nov 2012 20:04:41 +0100 [thread overview]
Message-ID: <20121107190441.GC24379@joi.lan> (raw)
In-Reply-To: <20121107000847.GA21065-yqdYmcOkqV0XGNroddHbYwC/G2K4zDHf@public.gmane.org>
On Wed, Nov 07, 2012 at 10:08:47AM +1000, Ben Skeggs wrote:
> On Tue, Nov 06, 2012 at 10:48:52PM +0100, Marcin Slusarz wrote:
> > Now it outputs:
> > nouveau E[ PGRAPH][0000:02:00.0] PGRAPH TLB flush idle timeout fail
> > nouveau E[ PGRAPH][0000:02:00.0] PGRAPH_STATUS: BUSY DISPATCH VFETCH CCACHE_UNK4 STRMOUT_GSCHED_UNK5 UNK14XX UNK1CXX CLIPID ZCULL ENG2D UNK34XX TPRAST TPROP ROP (0x011fde03)
> > nouveau E[ PGRAPH][0000:02:00.0] PGRAPH_VSTATUS: CCACHE (0x00145b4d) (0x0000002d) ENG2D ROP (0x0034db40)
>
> How about this instead?
>
> PGRAPH_STATUS : 0x011fde03 [BUSY DISPATCH VFETCH CCACHE_UNK4 STRMOUT_GSCHED_UNK5 UNK14XX UNK1CXX CLIPID ZCULL ENG2D UNK34XX TPRAST TPROP ROP]
> PGRAPH_VSTATUS0: 0x00145b4d [CCACHE]
> PGRAPH_VSTATUS1: 0x0000002d []
> PGRAPH_VSTATUS2: 0x0034db40 [ENG2D ROP]
Looks good too. I'll post updated patch tomorrow.
Marcin
next prev parent reply other threads:[~2012-11-07 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 21:48 [PATCH] drm/nv50: decode PGRAPH status registers on TLB flush fail Marcin Slusarz
[not found] ` <1352238533-14920-4-git-send-email-marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-11-07 0:08 ` Ben Skeggs
[not found] ` <20121107000847.GA21065-yqdYmcOkqV0XGNroddHbYwC/G2K4zDHf@public.gmane.org>
2012-11-07 19:04 ` Marcin Slusarz [this message]
[not found] ` <20121107190441.GC24379-OI9uyE9O0yo@public.gmane.org>
2012-11-11 18:52 ` Marcin Slusarz
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=20121107190441.GC24379@joi.lan \
--to=marcin.slusarz-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=skeggsb-Re5JQEeQqe8AvxtiuMwx3w@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.