From: "Jose Mª Ferreiro" <jose.ferreiro@horus.es>
To: meta-freescale@yoctoproject.org
Subject: Re: error(Segmentation fault) when i launch the gstreamer with "mfw_isink" in the second time
Date: Tue, 01 Oct 2013 15:21:33 +0200 [thread overview]
Message-ID: <524ACC5D.4060105@horus.es> (raw)
In-Reply-To: <CAP9ODKquBD8UZtsuiW1KC9osDV1JS_fJZE_eL2s8MazZMQ+u2A@mail.gmail.com>
El 01/10/2013 14:24, Otavio Salvador escribió:
> Hello Jose,
>
> On Tue, Oct 1, 2013 at 8:54 AM, Jose Mª Ferreiro <jose.ferreiro@horus.es> wrote:
>> El 29/09/2013 23:27, Otavio Salvador escribió:
>>
>>> On Sun, Sep 29, 2013 at 12:19 AM, jojo <rjiejie@gmail.com> wrote:
>>>> Anyone met this issue ?
>>>>
>>>> * The first time i launch the player with isink log as bellow :
>>>>
>>>> MAX resolution 1920x1080
>>>> set color key
>>>> MFW_GST_ISINK_PLUGIN 3.0.5 build on Sep 16 2013 14:09:24.
>>>> stream_mjpeg_init:265:streamer(1c7a00)
>>>> [INFO] Product Info: i.MX6Q/D/S
>>>> vpudec versions :)
>>>> plugin: 3.0.5
>>>> wrapper: 1.0.24(VPUWRAPPER_ARM_LINUX Build on Sep 12 2013
>>>> 10:39:29)
>>>> vpulib: 5.4.10
>>>> firmware: 2.1.8.34588
>>>> [INFO] bitstreamMode 1, chromaInterleave 0, mapType 0,
>>>> tiled2LinearEnable 0
>>>> hwbuf allocator zone(2306048) created
>>>> can not create threadmfw_gst_isink_setcaps:1489
>>>> VS0 created. in fmt[I420] win(0,0-1920,800:1920x800) out
>>>> win(0,140-1920,940:1920x800)
>>>> set deinterlace mode 0
>>>>
>>>>
>>>> * The log as bellow when i stop the streaming (stop the gstreamer pipe):
>>>>
>>>> VS0 destroyed, force=0!
>>>> hwbuf allocator zone(2306048) destroied.
>>>>
>>>>
>>>> * The second time i launch the player with isink log as bellow :
>>>>
>>>> set color key
>>>> MFW_GST_ISINK_PLUGIN 3.0.5 build on Sep 16 2013 14:09:24.
>>>> stream_mjpeg_init:265:streamer(1c8f90)
>>>> [INFO] Product Info: i.MX6Q/D/S
>>>> vpudec versions :)
>>>> plugin: 3.0.5
>>>> wrapper: 1.0.24(VPUWRAPPER_ARM_LINUX Build on Sep 12 2013
>>>> 10:39:29)
>>>> vpulib: 5.4.10
>>>> firmware: 2.1.8.34588
>>>> [INFO] bitstreamMode 1, chromaInterleave 0, mapType 0,
>>>> tiled2LinearEnable 0
>>>> hwbuf allocator zone(2306048) created
>>>> can not create threadmfw_gst_isink_setcaps:1489
>>>> VS0 created. in fmt[I420] win(0,0-1920,800:1920x800) out
>>>> win(0,140-1920,940:1920x800)
>>>> set deinterlace mode 0
>>>> Can not open dll, libgstfsl-0.10.so: cannot open shared object file: No
>>>> such
>>>> file or directory.
>>>> Segmentation fault
>>> ...
>>>
>>> Please try to reproduce it using 'dora' branch so we can know if it
>>> still happens or not.
>>>
>>> I think most of these issues has been fixed in last MM codecs releases
>>> so it's worth a try.
>>>
>> We are testing things with Gstreamer and run into a similar error. It does
>> the 'No such file or directory' thing but with 'Caught SIGSEGV accesing
>> address (nil)' message.
>>
>> We, newbies, dare to do:
>> cd /usr/lib
>> ln -s libgstfsl-0.10.so.0 libgstfsl-0.10.so
>> then reboot, and that message was over. Now we can run several times our
>> command.
> As far as I know we had fixed this in 'dora'.
>
>> Here is an iMX6Q Sabre Lite board, and it happens with yesterday
>> master+linux-imx and dora+linux-imx branches.
> Humm ... Daiane, can you try to reproduce this issue?
>
> Jose, can you report this issue in our bugzilla?
I found it was there already. I updated this:
*Bug 3781* <https://bugzilla.yoctoproject.org/show_bug.cgi?id=3781>
-i.MX6Q: mfw_isink Problem
Thank you
>> We have to change from linux-boundary to linux-imx because we moved to an
>> HDMI monitor. After that, linux-boundary hdmi driver keeps giving messages
>> and hanging the system.
> Eric, any clue here?
>
next prev parent reply other threads:[~2013-10-01 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 3:19 error(Segmentation fault) when i launch the gstreamer with "mfw_isink" in the second time jojo
2013-09-29 21:27 ` Otavio Salvador
2013-10-01 11:54 ` Jose Mª Ferreiro
2013-10-01 12:24 ` Otavio Salvador
2013-10-01 12:29 ` 回复: " jojo
2013-10-01 13:21 ` Jose Mª Ferreiro [this message]
2013-10-01 14:33 ` Eric Nelson
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=524ACC5D.4060105@horus.es \
--to=jose.ferreiro@horus.es \
--cc=meta-freescale@yoctoproject.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.