From: Arvind R <arvino55@gmail.com>
To: xen-devel@lists.xensource.com
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: [Code Trace] dom0 Nouveau accelerated mmap problem
Date: Sun, 28 Feb 2010 13:01:16 +0530 [thread overview]
Message-ID: <d799c4761002272331q38df6ba0k4472eca57cbe8a9b@mail.gmail.com> (raw)
Hi,
In continuation of my 'Nouveau on dom0' posting, I dug into the code ...
As Konrad had predicted, it is the discontinuous PFN in the mmapped
area that seems to the problem.
booted bare hardware
X: libdrm:OUT_RING: Enter: chan=0x8170a0, id=2, data=0x44000,
chan->cur=0x7fcdaff5e000
*(chan->cur++) = (data);
X: libdrm:OUT_RING: Exit
<some time later>
kernel: ttm_bo_vm_fault: bo=ffff88007ccfb200
kernel: ttm_bo_vm_fault: is_iomem=0, page_offset=0x0, page_last=0x10,
bo->num_pages=16
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff5e000,
pfn=0x73f95, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff5f000,
pfn=0x73f96, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff60000,
pfn=0x73f97, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff61000,
pfn=0x73f98, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff62000,
pfn=0x73f99, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff63000,
pfn=0x73f9a, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff64000,
pfn=0x73f9b, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff65000,
pfn=0x73f9c, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff66000,
pfn=0x73f9d, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff67000,
pfn=0x73f9e, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff68000,
pfn=0x73f9f, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff69000,
pfn=0x73fa0, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff6a000,
pfn=0x73fa1, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff6b000,
pfn=0x73fa2, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff6c000,
pfn=0x73fa3, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff6d000,
pfn=0x73fa4, ret=0
booted Xen
X: libdrm:OUT_RING: Enter: chan=0x8170a0, id=2, data=0x44000,
chan->cur=0x7faed9add000
<some time later, repeats never-ending till shutdown, OUT_RING never exits>
kernel: ttm_bo_vm_fault: bo=ffff88000e79ba00
kernel: ttm_bo_vm_fault: is_iomem=0, page_offset=0x0, page_last=0x10,
bo->num_pages=16
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9add000,
pfn=0xe6db, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ade000,
pfn=0xe718, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9adf000,
pfn=0xe772, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ae0000,
pfn=0xe778, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ae1000,
pfn=0xe6eb, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ae2000,
pfn=0xe738, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ae3000,
pfn=0xe6da, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ae4000,
pfn=0xe710, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ae5000,
pfn=0xe76e, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ae6000,
pfn=0xe7ad, ret=0
ttm_bo_vm_fault() is in drivers/gpu/drm/ttm/ttm_bo_vm.c in the kernel tree.
HELP!
Arvind R.
next reply other threads:[~2010-02-28 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 7:31 Arvind R [this message]
2010-03-01 16:55 ` [Code Trace] dom0 Nouveau accelerated mmap problem Konrad Rzeszutek Wilk
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=d799c4761002272331q38df6ba0k4472eca57cbe8a9b@mail.gmail.com \
--to=arvino55@gmail.com \
--cc=konrad.wilk@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).