[Sound-open-firmware] BYT; why is my logger not working?
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?
Thanks Guennadi
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
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/logger/...
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@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
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...
The test case is called check_sof_logger
Thanks Xiuli
-----Original Message----- From: Sound-open-firmware [mailto:sound-open-firmware-bounces@alsa- project.org] On Behalf Of Jankowski, Janusz Sent: Monday, May 6, 2019 06:13 To: sound-open-firmware@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/logger/... 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@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
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...
The test case is called check_sof_logger
Thanks Xiuli
-----Original Message----- From: Sound-open-firmware [mailto:sound-open-firmware-bounces@alsa- project.org] On Behalf Of Jankowski, Janusz Sent: Monday, May 6, 2019 06:13 To: sound-open-firmware@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/logger/... 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@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
Hi Xiuli,
Thanks for checking and confirming! It must be something with my setup then, I'll double-check, that I have all the newest sode on it.
Thanks Guennadi
On Tue, May 07, 2019 at 07:05:22AM +0000, Pan, Xiuli wrote:
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@linux.intel.com] Sent: Monday, May 6, 2019 14:56 To: Pan, Xiuli xiuli.pan@intel.com Cc: Jankowski, Janusz janusz.jankowski@linux.intel.com; sound-open- firmware@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.
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@alsa- project.org] On Behalf Of Jankowski, Janusz Sent: Monday, May 6, 2019 06:13 To: sound-open-firmware@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@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
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@linux.intel.com] Sent: Monday, May 6, 2019 14:56 To: Pan, Xiuli xiuli.pan@intel.com Cc: Jankowski, Janusz janusz.jankowski@linux.intel.com; sound-open- firmware@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.
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@alsa- project.org] On Behalf Of Jankowski, Janusz Sent: Monday, May 6, 2019 06:13 To: sound-open-firmware@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@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
Hi,
On Mon, 6 May 2019, Guennadi Liakhovetski wrote:
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?
please update your sof-logger binary to the latest one. I've made a few patches that will probably help. Specifically in trace mode (-t), if sog-logger gets an eof, it will reopen the file node.
This doesn't explain why you started seeing this on BYT, but might help nevertheless. The patches help on UP^2 as well to keep tracing going over S3 suspend/resume cycles.
Br, Kai
participants (5)
-
Guennadi Liakhovetski -
Jankowski, Janusz -
Kai Vehmanen -
Liam Girdwood -
Pan, Xiuli