Re: afm-mediaplayer-binding

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Could you send me the log without filtering it on service unit. Here we only see logs of the unit but I'd need the whole log sequence right after a boot. And also create a JIRA ticket at https://jira.automotivelinux.org/

We don't see where the crash occurs and which is the call that triggers the error. Discussing with Loïc, we wonder if there aren't a dependency problem with Unicens binding which maybe crash and so the rest... As he already experienced something similar.

We don't reproduce the error here so it is complicated to debug on our side.

Thanks.

On 08/15/2018 04:29 AM, Sitech wrote:
Hi friends,
I am really confused about the malloc crash issue. When i debug this issue, I found that it crashed in xxx/4a-softmixer/app-afb-helpers-submodule/filescan-utils.c 'ScanDir' function. At the very start, I think it maybe stack overflow because there is a recursion call and large array declaration, the problem cased malloc fail, so i modify the code and check the log(see them in attachment called 1.log ), but it still crashed. And then, I add some debug code and check the state, but i found it doesn't crash at this call(it still crashed in another call, please see them in attachment called 2.log), I could not understand this reason. And i notice that the log :
Aug  8 08:28:30 raspberrypi3 daemon.warn systemd[1]: afm-service-agl-service-audio-4a--1.0-11d2ae9--main@0.service: Start request repeated too quickly.

Does the issue have anything to do with it?

Thanks,
Sitech
 
------------------ Original ------------------
Date:  Tue, Aug 14, 2018 03:16 PM
To:  "thierry bultel"<thierry.bultel@xxxxxxx>;
Subject:  Re: afm-mediaplayer-binding
 
Hi Thierry,
Very thanks for your reply, i think the bug has been solved on their sides, but i still get this crash after i update my image on rpi3 board(All about 4a modules have already updated). I will track this issue, after i get my jira account, i will update to the jira.

Thanks,
Sitech
 
------------------ Original ------------------
Date:  Mon, Aug 13, 2018 08:36 PM
To:  "Sitech"<developer_agl@xxxxxxx>;
Subject:  Re: afm-mediaplayer-binding
 
Dear Sitech,

There is an existing & similar issue:

https://jira.automotivelinux.org/browse/SPEC-1639

That issue is fixed on master. To get it, you should
take the latest
- 4a-softmixer (https://github.com/iotbzh/4a-softmixer)
- 4a-hal-generic (https://github.com/iotbzh/4a-hal-generic)

Please tell us if it helps

Regards
Thierry

On 08/13/2018 10:17 AM, thierry bultel wrote:
> Dear Sitech,
>
> In your /var/log/messages, there is a very early crash of
> afbd-agl-service-audio-4a (see the sysmalloc error at 08:28:29)
> It is impossible to say what happens in this state, with only the log.
> I am afraid you will have to a little debugging to try to understand
> what is happening.
>
> If you feel confident in doing such, I would recommend starting 4a
> in standalone mode (ie, without systemd).
>
> For instance, after having recompiled all the bindings you need,
> and sent them on target with "make remote-target-populate" (you will
> have to create this file for the update configuration):
>
> ~/.config/app-templates/cmake.d/10-common-rsync.cmake
>
> set(RSYNC_PREFIX /tmp)
> set(RSYNC_TARGET root@X.X.X.X)
>
> ---------------------------------------------------------------
>
> Then, on target, this script launches 4a and it is easy to add gdb if
> needed.
>
> -------------------------------------
> #!/bin/bash
> set -x
>
> TOPDIR=/tmp
>
> /usr/bin/afb-daemon \
>
> --binding=$TOPDIR/4a-softmixer-latest/build_suse/mixer-binding/softmixer-binding.so
> \
>    --name=afb-4a \
>    --workdir=$TOPDIR/4a-softmixer-latest/build_suse \
>
> --binding=$TOPDIR/agl-service-audio-4a/build_suse/package/lib/afb-audiohighlevel.so
> \
>    --binding=$TOPDIR/4a-alsa-core/build_suse/alsa-binding/afb-alsa-4a.so\
>    --binding=$TOPDIR/4a-hal-generic/build_suse/4a-hal/4a-hal.so \
>    --no-ldpaths \
>    --port=1234 \
>    --token=\
>    --ws-server=unix:/run/user/0/apis/ws/ahl-4a
>    -vvv
> -----------------------------------------------
>
> Hope this helps
> Thierry
>
> On 08/11/2018 03:42 AM, Sitech wrote:
>> Hi bultel,
>> There is my /var/log/messages and dmesg log,, the DEFAULT_LOGLEVEL is
>> Log_Level_Warning, is that enough?
>>
>> Cheers,
>> Sitech
>>
>> ------------------ Original ------------------
>> *From: * "thierry bultel"<thierry.bultel@xxxxxxx>;
>> *Date: * Fri, Aug 10, 2018 07:43 PM
>> *To: * "Sitech"<developer_agl@xxxxxxx>;
>> *Cc:
>> * "automotive-discussions"<automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx>;
>>
>> *Subject: * Re: afm-mediaplayer-binding
>>
>>
>> On 08/10/2018 01:30 PM, Sitech wrote:
>>  > Hi bultel,
>>  > There is a file descriptor under the device node:
>>  >
>>  > raspberrypi3:/dev/snd/by-id# ls -al
>>  > total 0
>>  > drwxr-xr-x. 2 root root  60 Aug  8 08:49 .
>>  > drwxr-xr-x. 4 root root 380 Aug  8 08:49 ..
>>  > lrwxrwxrwx. 1 root root  12 Aug  8 08:49
>>  > usb-C-Media_Electronics_Inc._USB_Audio_Device-00 -> ../controlC2
>>  >
>>  > And i copy the "usb-C-Media_Electronics_Inc._USB_Audio_Device-00" and
>>  > write to the configuration file but it still doesn't work.  Does it
>> have
>>  > something to do with the '.'?
>>
>> The '.' should not be an issue at all.
>> Could you please show again your /var/log/message ?
>>
>> Should I configure others keys in the
>>  > .json file?
>>  > Now, i add a .asoundrc file at ~/ directory, and set external sound
>> card
>>  > as default sound card, it works temporarily. But i don't know why it
>>  > doesn't work when i modify the configuration file.
>>
>> 4a does not need a .asoundrc to work.
>>
>>  > And another question, i found that when 4a service start, a binding
>>  > called "4a hal manager" start also, but i didn' find the code on
>> gerrit,
>>  > and i also follow your github id, and IoT.bzh github id, still not
>>  > found, where could get the code? Thanks very much!
>>
>> It is at https://github.com/iotbzh/4a-hal-generic
>>
>>  >
>>  > Cheers,
>>  > Sitech
>>  > ------------------ Original ------------------
>>  > *From: * "thierry bultel"<thierry.bultel@xxxxxxx>;
>>  > *Date: * Fri, Aug 10, 2018 04:45 PM
>>  > *To:
>>  >
>> * "automotive-discussions"<automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx>;
>>
>>  >
>>  > *Subject: * Re: afm-mediaplayer-binding
>>  > Hi Sitech,
>>  >
>>  > Please have a look at the "playbacks" section in the .json file.
>>  > The playback device is identified by the /dev/snd/by-id entry
>>  >
>>  > In the version in git, you have
>>  > /dev/snd/by-id/usb-0d8c_USB_Sound_Device-00
>>  >
>>  > which is one of the devices we support and that is used in our tests.
>>  >
>>  > With aplay, it is listed as such:
>>  > card 2: Device [USB Sound Device], device 0: USB Audio [USB Audio]
>>  >     Subdevices: 1/1
>>  >     Subdevice #0: subdevice #0
>>  >
>>  > I am pretty sure that yours does not match this one, since on my side
>>  > the short name is "USB Sound Device" and on yours, it is "USB Audio
>> Device"
>>  >
>>  > Please check what you have in /dev/snd/by-id and try to put it in
>> the .json
>>  >
>>  > Cheers,
>>  > Thierry
>>  >
>>  > On 08/10/2018 07:01 AM, Sitech wrote:
>>  >  >
>>  >  > Hi friend,
>>  >  > Follow your advice, I buy a new simple usb sound card device,
>> the device
>>  >  > is ok, but still no sound, and the mail attachments is a picture
>> of my
>>  >  > platform, should i modify the "hal-4a-2ch-generic-usb.json"
>> file? By the
>>  >  > way, there are some log files, kernel.log & /var/log/messages.
>>  >  >
>>  >  > 1.
>>  >  > raspberrypi3:~/albert/log# aplay -l
>>  >  > **** List of PLAYBACK Hardware Devices ****
>>  >  > card 0: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM]
>>  >  >    Subdevices: 7/8
>>  >  >    Subdevice #0: subdevice #0
>>  >  >    Subdevice #1: subdevice #1
>>  >  >    Subdevice #2: subdevice #2
>>  >  >    Subdevice #3: subdevice #3
>>  >  >    Subdevice #4: subdevice #4
>>  >  >    Subdevice #5: subdevice #5
>>  >  >    Subdevice #6: subdevice #6
>>  >  >    Subdevice #7: subdevice #7
>>  >  > card 0: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM]
>>  >  >    Subdevices: 8/8
>>  >  >    Subdevice #0: subdevice #0
>>  >  >    Subdevice #1: subdevice #1
>>  >  >    Subdevice #2: subdevice #2
>>  >  >    Subdevice #3: subdevice #3
>>  >  >    Subdevice #4: subdevice #4
>>  >  >    Subdevice #5: subdevice #5
>>  >  >    Subdevice #6: subdevice #6
>>  >  >    Subdevice #7: subdevice #7
>>  >  > card 1: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
>>  >  >    Subdevices: 8/8
>>  >  >    Subdevice #0: subdevice #0
>>  >  >    Subdevice #1: subdevice #1
>>  >  >    Subdevice #2: subdevice #2
>>  >  >    Subdevice #3: subdevice #3
>>  >  >    Subdevice #4: subdevice #4
>>  >  >    Subdevice #5: subdevice #5
>>  >  >    Subdevice #6: subdevice #6
>>  >  >    Subdevice #7: subdevice #7
>>  >  > card 1: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835
>> IEC958/HDMI]
>>  >  >    Subdevices: 1/1
>>  >  >    Subdevice #0: subdevice #0
>>  >  > card 2: Device [USB Audio Device], device 0: USB Audio [USB Audio]
>>  >  >    Subdevices: 1/1
>>  >  >    Subdevice #0: subdevice #0
>>  >  > card 3: vc4hdmi [vc4-hdmi], device 0: MAI PCM vc4-hdmi-hifi-0 []
>>  >  >    Subdevices: 1/1
>>  >  >    Subdevice #0: subdevice #0
>>  >  >
>>  >  > 2.
>>  >  > raspberrypi3:~/albert/log# ls /media/ -al
>>  >  > total 40140
>>  >  > drwxr-xr-x   2 root root     4096 Aug  8 08:30 .
>>  >  > drwxr-xr-x  18 root root     4096 Aug  8  2018 ..
>>  >  > -rw-r--r--.  1 root root 41094140 Aug  8 08:30 Tyga - Taste.wav
>>  >  >
>>  >  > So, really hope more advices.
>>  >  > Cheers,
>>  >  > Sitech
>>  >  > ------------------ Original ------------------
>>  >  > *From: * "Sitech"<developer_agl@xxxxxxx>;
>>  >  > *Date: * Tue, Aug 7, 2018 06:37 PM
>>  >  > *To: * "Fulup Ar Foll"<fulup.arfoll@xxxxxxx>;
>>  >  >
>>  >
>> "automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx"<automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx>;
>>
>>  >
>>  >  >
>>  >  > *Subject: * Re: afm-mediaplayer-binding
>>  >  > Hello,
>>  >  > Very thanks for your apply! I will try to rebuild the project
>> and remove
>>  >  > pulseaudio.And as you said, I will try to fix the Rpi3 BSP problem.
>>  >  > Thanks.
>>  >  > ------------------ Original ------------------
>>  >  > *From: * "Fulup Ar Foll"<fulup.arfoll@xxxxxxx>;
>>  >  > *Date: * Tue, Aug 7, 2018 05:46 PM
>>  >  > *To: * "Sitech"<developer_agl@xxxxxxx>;
>>  >  >
>>  >
>> "automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx"<automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx>;
>>
>>  >
>>  >  >
>>  >  > *Subject: * Re: afm-mediaplayer-binding
>>  >  > Sitech
>>  >  >
>>  >  > As Loic said when using AGL/FF the media player should not rely on
>>  >  > pulse. Your log clearly shows that you try to start pulse, when it
>>  >  > should not. This should be easy to fix by using latest version
>> of FF.
>>  >  >
>>  >  > This being said with Rpi3 and ever version if Linux you use, you
>> should
>>  >  > face issues with the internal sound card. Alsa Mixer is broken and
>>  >  > unfortunately this issue does not depend on AGL, but is related to
>>  > Rpi3 BSP.
>>  >  >
>>  >  > Conclusion: 4A should work with AGL/FF on Rpi3 but only with an
>> external
>>  >  > sound card.
>>  >  >
>>  >  > Fulup
>>  >  >
>>  >  > On 06/08/18 08:15, Sitech wrote:
>>  >  >  > Hi all,
>>  >  >  > When I use mediaplayer to play the audio file, at first, I can
>>  > heard the
>>  >  >  > sound, but after one second, sound gone, and I check the log,
>> the
>>  > reason
>>  >  >  > is after this log, gstreamer couldn't read the audio streamer,as
>>  > follow:
>>  >  >  >
>>  >  >  > Jun 14 04:32:20 raspberrypi3 daemon.info pulseaudio[379]: E:
>>  >  >  > [pulseaudio] module-router.c: updating
>>  > source:ALSA#plug-in#[afb-daemon]
>>  >  >  > id=100
>>  >  >  > Jun 14 04:32:20 raspberrypi3 auth.notice dbus[280]: [system]
>> Rejected
>>  >  >  > send message, 0 matched rules; type="method_return",
>> sender=":1.20"
>>  >  >  > (uid=0 pid=379 comm="/usr/bin/pulseaudio --daemonize=no ")
>>  >  >  > interface="(unset)" member="(unset)" error name="(unset)"
>>  >  >  > requested_reply="0" d
>>  >  >  > Jun 14 04:32:20 raspberrypi3 auth.notice dbus[280]: [system]
>> Rejected
>>  >  >  > send message, 0 matched rules; type="method_return",
>> sender=":1.20"
>>  >  >  > (uid=0 pid=379 comm="/usr/bin/pulseaudio --daemonize=no ")
>>  >  >  > interface="(unset)" member="(unset)" error name="(unset)"
>>  >  >  > requested_reply="0" d
>>  >  >  > Jun 14 04:32:20 raspberrypi3 daemon.info pulseaudio[379]: E:
>>  >  >  > [pulseaudio] router-dbusif.c: source id = 100,source state = 1
>>  >  >  > Jun 14 04:32:20 raspberrypi3 auth.notice dbus[280]: [system]
>> Rejected
>>  >  >  > send message, 0 matched rules; type="method_return",
>> sender=":1.20"
>>  >  >  > (uid=0 pid=379 comm="/usr/bin/pulseaudio --daemonize=no ")
>>  >  >  > interface="(unset)" member="(unset)" error name="(unset)"
>>  >  >  > requested_reply="0" d
>>  >  >  >
>>  >  >  > and then, I check the code about pulseaudio, but I have no
>> idea to
>>  > debug
>>  >  >  > this problem. Does any friends meet this problem?
>>  >  >  >
>>  >  >  > Thanks
>>  >  >  >
>>  >  >  >
>>  >  >  > _______________________________________________
>>  >  >  > automotive-discussions mailing list
>>  >  >  > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
>>  >  >  >
>>  >
>> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
>>  >  >  >
>>  >  >
>>  >  >
>>  >  >
>>  >  > _______________________________________________
>>  >  > automotive-discussions mailing list
>>  >  > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
>>  >  >
>> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
>>  >  >
>>  > _______________________________________________
>>  > automotive-discussions mailing list
>>  > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
>>  >
>> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions


_______________________________________________
automotive-discussions mailing list
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions

-- 
Romain Forlot - Design Engineer - IoT.bzh
romain.forlot@xxxxxxx - www.iot.bzh - phone: +33675142438
_______________________________________________
automotive-discussions mailing list
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions

[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux