[Sound-open-firmware] BYT; why is my logger not working?

Pan, Xiuli xiuli.pan at intel.com
Tue May 7 09:05:22 CEST 2019


I did not see this issue with the latest daily build.
Please try to update all the binaries you are using.

I only see some IPC timeout when I try to stop the first play.

[  128.491618] sof-audio-acpi 80860F28:01: error: ipc timed out for 0x60050000 size 12
[  128.491712] sof-audio-acpi 80860F28:01: error: unexpected fault 0x600a0001 trace 0x60050000
[  128.491727] sof-audio-acpi 80860F28:01: error: waking up any trace sleepers
[  128.491752]  Low Latency: ASoC: trigger FE failed -110
[  128.491828] sof-audio-acpi 80860F28:01: error: trace IO error
[  128.492501] sof-audio-acpi 80860F28:01: pcm: free stream 0 dir 0
[  128.492521] sof-audio-acpi 80860F28:01: ipc tx: 0x60030000: GLB_STREAM_MSG: PCM_FREE
[  128.795450] sof-audio-acpi 80860F28:01: error: ipc timed out for 0x60030000 size 12
[  128.795530] sof-audio-acpi 80860F28:01: error: unexpected fault 0x600a0001 trace 0x60030000
[  128.795544] sof-audio-acpi 80860F28:01: error: waking up any trace sleepers


Thanks
Xiuli

>-----Original Message-----
>From: Guennadi Liakhovetski [mailto:guennadi.liakhovetski at linux.intel.com]
>Sent: Monday, May 6, 2019 14:56
>To: Pan, Xiuli <xiuli.pan at intel.com>
>Cc: Jankowski, Janusz <janusz.jankowski at linux.intel.com>; sound-open-
>firmware at alsa-project.org
>Subject: Re: [Sound-open-firmware] BYT; why is my logger not working?
>
>Hi,
>
>What I am seeing here is, that I get traces but then the logger
>immediately terminates instead of waiting for further data like
>e.g. on Up^2. Is this an intrinsic limitation on BYT?
>
>Thanks
>Guennadi
>On Mon, May 06, 2019 at 05:26:13PM +0000, Pan, Xiuli wrote:
>> Hi all,
>>
>> The sof-logger is already in sof ci on-device test already. We did not see any
>issue with BYT test cases.
>> Please see following link for detail.
>>
>> https://sof-
>ci.01.org/sofpr/PR1372/build1881/devicetest/BYT_MB_NOCODEC/check_sof_l
>ogger.sh/check_sof_logger.sh.txt
>>
>> The test case is called check_sof_logger
>>
>> Thanks
>> Xiuli
>>
>> >-----Original Message-----
>> >From: Sound-open-firmware [mailto:sound-open-firmware-bounces at alsa-
>> >project.org] On Behalf Of Jankowski, Janusz
>> >Sent: Monday, May 6, 2019 06:13
>> >To: sound-open-firmware at alsa-project.org
>> >Subject: Re: [Sound-open-firmware] BYT; why is my logger not working?
>> >
>> >CI only checks if it builds. To check if it works you need to feed it
>> >with data from memwindow with traces - in realtime (pipe) or just with
>> >binary file that has contents from that memwnd. You didn't write how you
>> >run it so it's hard to say why it closes with no output. Please note
>> >there are some docs regarding logger:
>> >https://thesofproject.github.io/latest/developer_guides/debugability/logg
>er/i
>> >ndex.html
>> >
>> >On 06.05.2019 15:05, Liam Girdwood wrote:
>> >> On Mon, 2019-05-06 at 12:58 +0200, Guennadi Liakhovetski wrote:
>> >>> Hi,
>> >>>
>> >>> Since noone else is reporting thic including CI, I assume it's me
>> >>> doing something wrong. sof-logger on minnow board exits immediately
>> >>> for me with no output. Could someone confirm or double-check?
>> >>>
>> >> Afaik, logger is not included in the CI atm. Maybe Xiuli has future plans for
>> >> this though.
>> >>
>> >> Can you raise as a regression with any suspicious output in dmesg.
>> >>
>> >> Liam
>> >>
>> >> _______________________________________________
>> >> Sound-open-firmware mailing list
>> >> Sound-open-firmware at alsa-project.org
>> >> https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
>> >_______________________________________________
>> >Sound-open-firmware mailing list
>> >Sound-open-firmware at alsa-project.org
>> >https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
>> _______________________________________________
>> Sound-open-firmware mailing list
>> Sound-open-firmware at alsa-project.org
>> https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware


More information about the Sound-open-firmware mailing list