From: Wang Diancheng <dcwang@redflag-linux.com>
To: linux-omap@vger.kernel.org
Subject: omap24xxvout alloc DMA page failed when using openMAX
Date: Mon, 16 Feb 2009 17:14:34 +0800 [thread overview]
Message-ID: <87fxien3ph.fsf@redflag-linux.com> (raw)
Hey, I posted this independently, and someone suggested I should send
it to this mailing list.
I don't read the list, so I'm not sure if this is useful or on-topic
or what. My apologies in advance if this is noise.
omap24xxvout alloc DMA page failed when I use openMAX on ZOOM2 board,
following is my test command and output:
gst-launch videotestsrc ! goosink_pp
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
^CVIDIOC_STREAMON: Cannot allocate memory
Caught interrupt -- handling interrupt.
root@omap-3430sdp:/mm/bin# gst-launch-0.10: page allocation failure. order:10, mode:0xd1
[<c0032348>] (dump_stack+0x0/0x14) from [<c009323c>] (__alloc_pages_internal+0x3ac/0x3c4)
[<c0092e90>] (__alloc_pages_internal+0x0/0x3c4) from [<c0033b58>] (__dma_alloc+0x160/0x3a0)
[<c00339f8>] (__dma_alloc+0x0/0x3a0) from [<c0033e20>] (dma_alloc_coherent+0x58/0x64)
[<c0033dc8>] (dma_alloc_coherent+0x0/0x64) from [<c01cf280>] (omap24xxvout_do_ioctl+0x10cc/0x1604)
r7:c6465e38 r6:c7275c00 r5:c7275c00 r4:002d9000
[<c01ce1b4>] (omap24xxvout_do_ioctl+0x0/0x1604) from [<c01c66a4>] (video_usercopy+0x1b8/0x2b8)
[<c01c64ec>] (video_usercopy+0x0/0x2b8) from [<c01cf918>] (omap24xxvout_ioctl+0xdc/0xec)
[<c01cf83c>] (omap24xxvout_ioctl+0x0/0xec) from [<c00bb064>] (vfs_ioctl+0x68/0x78)
[<c00baffc>] (vfs_ioctl+0x0/0x78) from [<c00bb2e4>] (do_vfs_ioctl+0x270/0x280)
r5:410bfc94 r4:c64f9440
[<c00bb074>] (do_vfs_ioctl+0x0/0x280) from [<c00bb334>] (sys_ioctl+0x40/0x64)
r7:c64f9440 r6:40045612 r5:410bfc94 r4:00000010
[<c00bb2f4>] (sys_ioctl+0x0/0x64) from [<c002dbe0>] (ret_fast_syscall+0x0/0x2c)
r7:00000036 r6:0009c2c0 r5:40896128 r4:410bfc94
Mem-info:
DMA per-cpu:
CPU 0: hi: 42, btch: 7 usd: 0
Active:8385 inactive:2703 dirty:0 writeback:0 unstable:0
free:13840 slab:1054 mapped:3488 pagetables:174 bounce:0
DMA free:55360kB min:1440kB low:1800kB high:2160kB active:33540kB inactive:10812kB present:130048kB pages_scanned:0 al
l_unreclaimable? no
lowmem_reserve[]: 0 0 0
DMA: 264*4kB 160*8kB 100*16kB 169*32kB 87*64kB 30*128kB 21*256kB 19*512kB 9*1024kB 6*2048kB 0*4096kB = 55360kB
4351 total pagecache pages
0 pages in swap cache
Swap cache stats: add 0, delete 0, find 0/0
Free swap = 0kB
Total swap = 0kB
32768 pages of RAM
14017 free pages
5862 reserved pages
1054 slab pages
4522 pages shared
0 pages swap cached
omap24xxfb_blank: vsyn wait failed
Thanks .
All sounds from you will really be appreciated.
Best Regards.
next reply other threads:[~2009-02-16 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 9:14 Wang Diancheng [this message]
2009-02-16 10:03 ` omap24xxvout alloc DMA page failed when using openMAX Felipe Contreras
2009-02-16 22:06 ` Daniel Díaz
2009-02-19 6:37 ` Wang Diancheng
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=87fxien3ph.fsf@redflag-linux.com \
--to=dcwang@redflag-linux.com \
--cc=linux-omap@vger.kernel.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.