From: Konrad Rzeszutek Wilk <konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Younes Manton <younes.m-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: PFIFO_DMA_PUSHER + Xen + NV30 + questions.
Date: Wed, 9 Jun 2010 09:47:20 -0400 [thread overview]
Message-ID: <20100609134720.GA7131@phenom.dumpdata.com> (raw)
In-Reply-To: <AANLkTimyQzqCw1QnSNxmUvilOqaWe60twrNGo4n8BIcx-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
> > I've fleshed out most of them (like GART had the wrong phys addresses,
> > ouch!), but the one that I am stumbling at is that I see the PFIFO_DMA_PUSHER,
> > which I am to understand means: "Oh, the GPU obj operation you stuck on the
> > RAMHT/RAMIN is busted."
.. snip ..
> buffer. Either you pointed the card at garbage instead of a sensible
> buffer (nv10_fifo_create_context for nv30 IIRC) or your initial
> pushbuf (submitted by nouveau_dma_init) contains garbage. Or maybe
> something else, but based on your log that would be my guess.
That was it. I had the physical addresses of the buffers properly put in
the GATT, but the physical address the GATT page directory that was programmed in
the GART was completly bogus. So the GART on behalf of the card, ended up reading
bogus addresses. Ouch.
Now of to fix vmap faults.
prev parent reply other threads:[~2010-06-09 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 21:24 PFIFO_DMA_PUSHER + Xen + NV30 + questions Konrad Rzeszutek Wilk
[not found] ` <20100604212455.GA7143-6K5HmflnPlqSPmnEAIUT9EEOCMrvLtNR@public.gmane.org>
2010-06-04 22:02 ` Younes Manton
[not found] ` <AANLkTimyQzqCw1QnSNxmUvilOqaWe60twrNGo4n8BIcx-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-09 13:47 ` Konrad Rzeszutek Wilk [this message]
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=20100609134720.GA7131@phenom.dumpdata.com \
--to=konrad.wilk-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=younes.m-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.