omap24xxvout alloc DMA page failed when using openMAX

omap24xxvout alloc DMA page failed when using openMAX

[Wang Diancheng]

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.

Re: omap24xxvout alloc DMA page failed when using openMAX

[Felipe Contreras]

On Mon, Feb 16, 2009 at 11:14 AM, Wang Diancheng
<dcwang@redflag-linux.com> wrote:
> 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.

I'm cc'ing Daniel Díaz, who should know about gst-goo.

Also, you can try gst-omapfb instead:
http://github.com/felipec/gst-omapfb

-- 
Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: omap24xxvout alloc DMA page failed when using openMAX

[Daniel Díaz]

Hello!

If you don't mind the top-posting, please see the quoted chain of
emails below. Summary is that some changes need to make it to the
omapzoom.org kernel for Zoom2.

Greetings!

Daniel Díaz
ddiaz@ti.com



________________________________________
From: Jimenez Villareal, Omar
Sent: Monday, February 16, 2009 11:46 AM
To: Mande, Nikhil; Turquette, Mike; Diaz, Daniel; Castaneda Gonzalez,
Axel; Munoz, Jose Luis Diaz
Subject: RE: omap24xxvout alloc DMA page failed when using openMAX

This bootargs are needed since 23.12 release because of memory
allocation at boot time but in omap zoom this changes are not merged,
first need to be done changes in omap zoom kernel and then when merged
720p resolution support this bootargs will be needed.

Regards,

Omar Jimenez
________________________________________
De: Mande, Nikhil
Enviado el: lunes, 16 de febrero de 2009 10:42 a.m.
Para: Turquette, Mike; Jimenez Villareal, Omar; Diaz, Daniel;
Castaneda Gonzalez, Axel; Munoz, Jose Luis Diaz
Asunto: RE: omap24xxvout alloc DMA page failed when using openMAX

They are related. Both kernel changes and those bootargs are required.

-----Original Message-----
From: Turquette, Mike
Sent: Monday, February 16, 2009 10:32 AM
To: Jimenez Villareal, Omar; Mande, Nikhil; Diaz, Daniel; Castaneda
Gonzalez, Axel; Munoz, Jose Luis Diaz
Subject: RE: omap24xxvout alloc DMA page failed when using openMAX

This is probably unrelated, but I saw in another thread by Lajos that
it is necessary to set omap24xxfb:rotation=0 in the bootargs to avoid
some errors when specifically using the Zoom2 board.

Obviously a rotation of 0 is the default, but Lajos said it had to be
specifically set to avoid some sort of issue.  Maybe related, maybe
not.

Mike

> -----Original Message-----
> From: Jimenez Villareal, Omar
> Sent: Monday, February 16, 2009 9:57 AM
> To: Mande, Nikhil; Diaz, Daniel; Turquette, Mike; Castaneda Gonzalez, Axel;
> Munoz, Jose Luis Diaz
> Subject: RE: omap24xxvout alloc DMA page failed when using openMAX
>
> Hi all,
>
> You are rigth, we are working to send the patches to sync up omap zoom with
> 23x, with these changes this issue is gone.
>
> We will keep you updated when this get ready,
>
> Thanks,
>
> Omar Jimenez
> ________________________________________
> De: Mande, Nikhil
> Enviado el: lunes, 16 de febrero de 2009 09:36 a.m.
> Para: Diaz, Daniel; Turquette, Mike
> CC: Jimenez Villareal, Omar
> Asunto: RE: omap24xxvout alloc DMA page failed when using openMAX
>
> Some changes in L23.x kernel are not merged into OMAPZoom kernel yet.
> Now we reserve memory required by display driver at boot time, so we don't run
> into this issue.
>
> Omar,
>   I believe we are merging these changes for L23.14, right?
>
> Thanks,
> Nikhil
>
> -----Original Message-----
> From: Diaz, Daniel
> Sent: Monday, February 16, 2009 9:22 AM
> To: Mande, Nikhil; Turquette, Mike
> Subject: FW: omap24xxvout alloc DMA page failed when using openMAX
>
> Hello!
>
> Do you guys have any information on this? This appeared on the linux-omap
> mailing list.
>
> Greetings!
>
> Daniel Díaz
> ddiaz@ti.com
>
>
>
> ________________________________________
> From: Felipe Contreras [felipe.contreras@gmail.com]
> Sent: Monday, February 16, 2009 4:03 AM
> To: Wang Diancheng
> Cc: linux-omap@vger.kernel.org; Diaz, Daniel
> Subject: Re: omap24xxvout alloc DMA page failed when using openMAX
>
> On Mon, Feb 16, 2009 at 11:14 AM, Wang Diancheng
> <dcwang@redflag-linux.com> wrote:
> > 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.
>
> I'm cc'ing Daniel Díaz, who should know about gst-goo.
>
> Also, you can try gst-omapfb instead:
> http://github.com/felipec/gst-omapfb
>
> --
> Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: omap24xxvout alloc DMA page failed when using openMAX

[Wang Diancheng]

Hi Daniel and Felipe,
Thank you for your reply,
has the patch fixing this issue merged to omapzoom.org?
I try again with today's kernel and same command, but failed again.

Best Regards,

Diancheng

>>>>> Daniel D韆z <mrchapp@gmail.com> writes:

    > Hello!  If you don't mind the top-posting, please see the quoted
    > chain of emails below. Summary is that some changes need to make
    > it to the omapzoom.org kernel for Zoom2.

    > Greetings!

    > Daniel D韆z ddiaz@ti.com



    > ________________________________________ From: Jimenez Villareal,
    > Omar Sent: Monday, February 16, 2009 11:46 AM To: Mande, Nikhil;
    > Turquette, Mike; Diaz, Daniel; Castaneda Gonzalez, Axel; Munoz,
    > Jose Luis Diaz Subject: RE: omap24xxvout alloc DMA page failed
    > when using openMAX

    > This bootargs are needed since 23.12 release because of memory
    > allocation at boot time but in omap zoom this changes are not
    > merged, first need to be done changes in omap zoom kernel and then
    > when merged 720p resolution support this bootargs will be needed.

    > Regards,

    > Omar Jimenez ________________________________________ De: Mande,
    > Nikhil Enviado el: lunes, 16 de febrero de 2009 10:42 a.m.  Para:
    > Turquette, Mike; Jimenez Villareal, Omar; Diaz, Daniel; Castaneda
    > Gonzalez, Axel; Munoz, Jose Luis Diaz Asunto: RE: omap24xxvout
    > alloc DMA page failed when using openMAX

    > They are related. Both kernel changes and those bootargs are
    > required.

    > -----Original Message----- From: Turquette, Mike Sent: Monday,
    > February 16, 2009 10:32 AM To: Jimenez Villareal, Omar; Mande,
    > Nikhil; Diaz, Daniel; Castaneda Gonzalez, Axel; Munoz, Jose Luis
    > Diaz Subject: RE: omap24xxvout alloc DMA page failed when using
    > openMAX

    > This is probably unrelated, but I saw in another thread by Lajos
    > that it is necessary to set omap24xxfb:rotation=0 in the bootargs
    > to avoid some errors when specifically using the Zoom2 board.

    > Obviously a rotation of 0 is the default, but Lajos said it had to
    > be specifically set to avoid some sort of issue.  Maybe related,
    > maybe not.

    > Mike

    >> -----Original Message----- From: Jimenez Villareal, Omar Sent:
    >> Monday, February 16, 2009 9:57 AM To: Mande, Nikhil; Diaz,
    >> Daniel; Turquette, Mike; Castaneda Gonzalez, Axel; Munoz, Jose
    >> Luis Diaz Subject: RE: omap24xxvout alloc DMA page failed when
    >> using openMAX
    >> 
    >> Hi all,
    >> 
    >> You are rigth, we are working to send the patches to sync up omap
    >> zoom with 23x, with these changes this issue is gone.
    >> 
    >> We will keep you updated when this get ready,
    >> 
    >> Thanks,
    >> 
    >> Omar Jimenez ________________________________________ De: Mande,
    >> Nikhil Enviado el: lunes, 16 de febrero de 2009 09:36 a.m.  Para:
    >> Diaz, Daniel; Turquette, Mike CC: Jimenez Villareal, Omar Asunto:
    >> RE: omap24xxvout alloc DMA page failed when using openMAX
    >> 
    >> Some changes in L23.x kernel are not merged into OMAPZoom kernel
    >> yet.  Now we reserve memory required by display driver at boot
    >> time, so we don't run into this issue.
    >> 
    >> Omar, I believe we are merging these changes for L23.14, right?
    >> 
    >> Thanks, Nikhil
    >> 
    >> -----Original Message----- From: Diaz, Daniel Sent: Monday,
    >> February 16, 2009 9:22 AM To: Mande, Nikhil; Turquette, Mike
    >> Subject: FW: omap24xxvout alloc DMA page failed when using
    >> openMAX
    >> 
    >> Hello!
    >> 
    >> Do you guys have any information on this? This appeared on the
    >> linux-omap mailing list.
    >> 
    >> Greetings!
    >> 
    >> Daniel D韆z ddiaz@ti.com
    >> 
    >> 
    >> 
    >> ________________________________________ From: Felipe Contreras
    >> [felipe.contreras@gmail.com] Sent: Monday, February 16, 2009 4:03
    >> AM To: Wang Diancheng Cc: linux-omap@vger.kernel.org; Diaz,
    >> Daniel Subject: Re: omap24xxvout alloc DMA page failed when using
    >> openMAX
    >> 
    >> On Mon, Feb 16, 2009 at 11:14 AM, Wang Diancheng
    >> <dcwang@redflag-linux.com> wrote:
    >> > 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.
    >> 
    >> I'm cc'ing Daniel D韆z, who should know about gst-goo.
    >> 
    >> Also, you can try gst-omapfb instead:
    >> http://github.com/felipec/gst-omapfb
    >> 
    >> -- Felipe Contreras

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html