All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Michael D Labriola <mlabriol@gdeb.com>
Cc: Arvind R <arvino55@gmail.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	xen-devel@lists.xensource.com,
	Joanna Rutkowska <joanna@invisiblethingslab.com>,
	xen-devel-bounces@lists.xensource.com
Subject: Re: Re: [Patch RFC] ttm: nouveau accelerated on Xen pv-ops kernel
Date: Tue, 16 Mar 2010 13:21:35 -0400	[thread overview]
Message-ID: <20100316172135.GA25753@phenom.dumpdata.com> (raw)
In-Reply-To: <OFDB580600.A083B538-ON852576E8.005B22A4-852576E8.005B97C0@gdeb.com>

> > > And my X log ends abruptly after this line:
> > > (II) NOUVEAU(0): Opened GPU Channel 1
> > >
> > > Any ideas?
> > > 
> > 
> > Well, this is generally the symptom that someone is confusing mfns and 
> > pfns, and therefore ends up incorrectly setting the _PAGE_IO flag in 
> > some pte.  If you run it under strace, can you identify which mapping 
> > the fault is happening in?
> 
> I've attached the output of 'strace -o strace-Xorg Xorg'.  Figuring out 
> which mapping the fault is happening in is a little over my head, I'm 
> afraid.  If you need different arguments to strace, let me know and I'll 
> do it again.

So just to be sure, you took the 2.6.32 (xen/next or
xen/stable-2.6.32.x), copied the include and nouveu directory from ..?
2.6.33? and then ran this. Did you have to edit your xorg.conf file or
it ran just fine? Was this Fedora 13 or Fedora 12?

Arvind explanation about the Nvidia driver pointed out that the NVidia
driver (drm/nouvue) can operate on different channels. Where channel 1
is the framebuffer, and the other are for well, KMS, and other
applications.

I belive I was looking at the wrong section of the drivers (not the
drivers/video/gpu ones)- this certainly looks to be the issues the Jeremy mentioned.

Also I would suggest you load drm with the debug variable set to the 255
to get most of what his happening. 

Based on your strace, the last call is:
4000)                          = 0x9324000
write(0, "(II) NOUVEAU(0): Opened GPU chan"..., 38) = 38 
ioctl(11, 0xc0106445, 0x930a908)        = 0  
ioctl(11, 0x400c6444, 0xbfd2a210)       = 0  
+++ killed by SIGKILL +++

I cannot find what 0x45 is in the upstream Linux, so you must be using a
different nouv* driver than that. The 0x44 is:

  DRM_IOCTL_DEF(DRM_NOUVEAU_GEM_INFO, nouveau_gem_ioctl_info, DRM_AUTH),

Which looks to be pretty harmless. I presume it is the next thing (using
the address returned) that the X driver tries to do that makes it go boom.

  reply	other threads:[~2010-03-16 17:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 13:21 [Patch RFC] nouveau accelerated on Xen pv-ops kernel Arvind R
     [not found] ` <d799c4761003100521h663c82eepda85f3f0309828c2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-11 11:02   ` [Patch RFC] ttm: " Pekka Paalanen
2010-03-12  5:27     ` Arvind R
2010-03-28 10:20       ` Joanna Rutkowska
2010-03-30  5:50         ` Arvind R
2010-03-12 12:45     ` Arvind R
2010-03-12 13:20       ` Michael D Labriola
2010-03-13 22:03       ` Joanna Rutkowska
2010-03-15 14:44         ` Michael D Labriola
2010-03-15 23:13           ` Jeremy Fitzhardinge
2010-03-16  7:18             ` Arvind R
2010-03-16 16:48               ` Michael D Labriola
2010-03-16 16:40             ` Michael D Labriola
2010-03-16 17:21               ` Konrad Rzeszutek Wilk [this message]
2010-03-16 19:39                 ` Michael D Labriola
2010-03-16 19:41                   ` Konrad Rzeszutek Wilk
2010-03-17  1:01                     ` Konrad Rzeszutek Wilk
2010-03-18  6:09                   ` Arvind R
2010-03-19 15:29                     ` Michael D Labriola
2010-03-20  6:01                       ` Arvind R
2010-03-22 21:14                         ` Michael D Labriola
2010-03-23  6:21                           ` Arvind R
2010-03-23 12:45                             ` Michael D Labriola
2010-03-23 13:27                             ` Michael D Labriola
2010-03-25  7:05                               ` Arvind R
2010-03-25  7:18           ` Jeremy Fitzhardinge
2010-03-29 14:42             ` Michael D Labriola
2010-06-09 17:43           ` Konrad Rzeszutek Wilk
2010-06-09 18:39             ` Pasi Kärkkäinen
2010-06-09 19:31               ` Konrad Rzeszutek Wilk
2010-06-17 17:51             ` Konrad Rzeszutek Wilk
2010-06-22 22:32               ` Joanna Rutkowska
2010-06-23 12:54                 ` Konrad Rzeszutek Wilk
2010-06-23 13:21                   ` Joanna Rutkowska
2010-06-23 14:38                     ` Konrad Rzeszutek Wilk
2010-06-23 15:08                       ` Konrad Rzeszutek Wilk
2010-06-24 19:55                   ` Pasi Kärkkäinen
2010-06-24 21:00                     ` Konrad Rzeszutek Wilk
     [not found]       ` <d799c4761003120445h57ab1373m31eb0add242ef74c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-16 13:25         ` Thomas Hellstrom

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=20100316172135.GA25753@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=arvino55@gmail.com \
    --cc=jeremy@goop.org \
    --cc=joanna@invisiblethingslab.com \
    --cc=mlabriol@gdeb.com \
    --cc=xen-devel-bounces@lists.xensource.com \
    --cc=xen-devel@lists.xensource.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.