You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@cujomalainey Only 1 binary of sof-logger is built in the make process, You probably have some leftovers from previous runs. Please cleanup your workspace, e.g. git clean -f @ZhendanYang Please verify if the issue occurs on revisions following PR #490 and update this issue accordingly. Thank you.
Activity
cujomalainey commentedon Oct 10, 2018
See #473 for similar symptoms
akloniex commentedon Oct 16, 2018
@xiulipan @cujomalainey
PR addessing this issue was merged. Please verify and update this issue accordingly,
lgirdwood commentedon Oct 16, 2018
@ZhendanYang needs validated and closed.
ZhendanYang commentedon Oct 17, 2018
On up2 with nocodec, rmbox and logger are still empty, while rmbox -t and logger -t are not.
cujomalainey commentedon Oct 17, 2018
Still seeing empty logs as well on glk with sof_logger -t
cujomalainey commentedon Oct 17, 2018
@akloniex why are there two logger binaries? Which one am I supposed to be using? We should delete the other one otherwise this is confusing.
akloniex commentedon Oct 23, 2018
@cujomalainey Only 1 binary of sof-logger is built in the make process, You probably have some leftovers from previous runs. Please cleanup your workspace, e.g. git clean -f
@ZhendanYang Please verify if the issue occurs on revisions following PR #490 and update this issue accordingly. Thank you.
cujomalainey commentedon Oct 23, 2018
@akloniex yep that was the issue. Sorry, I should have checked that before. I was thrown by the simultaneous name change and location move.
ZhendanYang commentedon Oct 24, 2018
@akloniex
I did some tests on up2 with codec. I introduced XRUN injection when playback. and sof-logger -t showed some errors in red color words:
But sof-logger without the parameter -t still showed nothing:
yzd@up-03:~/test-10.23$ sudo ./sof-logger -l sof-apl.ldc-master-gcc
CORE LEVEL COMP_ID TIMESTAMP DELTA FILE_NAME CONTENT
Test env:
sof-master: 6baff99
soft-master: a1dfcb7
kernel sof-dev: 7ef809d
tplg: sof-apl-pcm512x.tplg
mengdonglin commentedon Oct 24, 2018
@ZhendanYang @keqiaozhang logger will output to different file w/o parameter -t. Please check thesofproject/soft#104 and check if this is a fake issue.
Jiangxinx commentedon Oct 25, 2018
sof-logger without the parameter -t can show error trace.
STEP:
1.aplay -Dhw:0,1 audio.wav
2.sudo ./xrun_injection.sh
3.sudo sof-logger -l sof-apl.ldc -o logger.log
Test env:
hardware version: UP2
sof-master: b793f0c
soft-master: c9a4c87
kernel sof-dev: fe8404a
tplg: sof-apl-pcm512x.tplg
Log:
dmesg.log
logger.log
xiulipan commentedon Oct 25, 2018
I think this issue is fixed with b015076 from #490
Jiangxinx commentedon Oct 30, 2018
Not reproduced with kernel branch debug/v4.19-backport, on APL UP2 platfrom.
STEP:
1.aplay -Dhw:0,0 audio.wav
2.sudo ./xrun_injection.sh
3.sudo sof-logger -l sof-apl.ldc -o logger.log
Test env:
hardware version: UP2
sof-master: 04b1ce4
soft-master: 4ac9248
kernel debug/v4.19-backport: e7da1c4
tplg: sof-apl-pcm512x.tplg
Jiangxinx commentedon Nov 1, 2018
Not reproduced with kernel branch debug/v4.19-backport, on APL UP2 platfrom.
STEP:
1.aplay -Dhw:0,0 audio.wav
2.sudo ./xrun_injection.sh
3.sudo sof-logger -l sof-apl.ldc -o logger.log
Test env:
hardware version: UP2
sof-master: 43da169
soft-master: 4ac9248
kernel debug/v4.19-backport: 925637e3
tplg: sof-apl-pcm512x.tplg
keqiaozhang commentedon Nov 1, 2018
Confirmed that this issue is fixed on Yorp.
Test with:
soft-master:4ac9248f
sof-master:43da16
kernel-debug/cros-v4.14-rebase: 90eee4