Open keqiaozhang opened 7 months ago
probably the same as https://github.com/thesofproject/linux/issues/4754, it's not worth investigating audio quality issues until fw-based aggregation is merged in firmware and kernel
probably the same as thesofproject/linux#4754, it's not worth investigating audio quality issues until fw-based aggregation is merged in firmware and kernel
Ok, lets wait until aggregation is fully ready. I've put in v2.10 for the moment, can be moved to v2.9 if needed.
@plbossart @bardliao @ujfalusi whats the status today ?
I don't think we can reach any conclusions, we still have FAILs in alsa-bat, and I don't get if this is still related to the jack setup or now.
@plbossart @lgirdwood I checked some recent daily test results, check-alsabat-headset-playback seems pass consistently and some of the check-alsabat-headset-capture are failed. But they are all because of the signal is too low not like this issue's description. And the issue is tracking at https://github.com/thesofproject/linux/issues/5076.
But the reproduction rate of this issue is low. So, I don't know if it is fixed or just not reproduced recently.
@fredoh9 @marc-hb @ssavati anyone seen this on daily test recently ? If not we can close. This is different from the bank switch and missing IRQ.
I cannot find anything like this, but we have at least two corrupted alsabat: https://sof-ci.ostc.intel.com/#/result/planresultdetail/41949?model=LNLM_SDW_AIOC&testcase=check-alsabat-headset-playback-599 https://sof-ci.ostc.intel.com/#/result/planresultdetail/41810?model=LNLM_SDW_AIOC&testcase=check-alsabat-headset-playback-599
we are not even looking at quality issues for now, the priority is to deal with timeouts.
I've seen this "Underrun: Broken pipe" recently. Also, alsabat (which is the only "real" audio test in sof-test) is still failing left and right on LNL.
I've seen this "Underrun: Broken pipe" recently.
One just now:
One just now:
- [LNL HDA alsabat capture failed, "Peak freq too low" #9164 (comment)]
Different issue. We're tracking SoundWire issues here, the HDA alsabat stuff is a different problem relying on a different topology and a different physical interface/timing.
Sorry my bad, went too fast. To make amend, here's the SDW, "signal too weak" failure of the day:
... and still wrong, there is yet another issue about that: thesofproject/linux#5076. Really sorry, I'm losing track
Reproduction rate low in past week, continue with P2 and assign to v2.11.
Recent "Underrun: Broken pipe(-32)" in https://sof-ci.01.org/softestpr/PR1217/build594/devicetest/index.html?model=LNLM_SDW_AIOC&testcase=check-alsabat-headset-playback-599
EDIT: also an overrun in https://github.com/thesofproject/linux/issues/5076#issuecomment-2231565735
Still failing, August 14th https://sof-ci.01.org/sofpr/PR9351/build6997/devicetest/index.html?model=LNLM_SDW_AIOC&testcase=check-alsabat-headset-playback-599
Reviewing a week worth of daily test plans with this configurations (starting 2024-09-02), this test is passing all the time. It is likely https://github.com/zephyrproject-rtos/zephyr/pull/77805 fix was responsible for the occasional 1ms glitches seen in this test and those are now gone.
Murphy's law, the next daily plan shows a fail again, 2024-09-09 run has a fail. Console has a overrun and the captured bat.wav look like this:
... rest of file is clean. Reopening.
@kv2019i please create new ticket for this problem
@lrudyX can you summarize how it is a different issue now?
@lrudyX I think this is exactly the original problem (quoting the original bug report from January):
2024-01-28 22:11:39 UTC [REMOTE_INFO] Starting /usr/local/bin/mtrace-reader.py >& /home/ubuntu/sof-test/logs/check-alsabat/2024-01-28-22:11:38-10012/mtrace.txt &
2024-01-28 22:11:39 UTC [REMOTE_INFO] check the PCMs before alsabat test
2024-01-28 22:11:41 UTC [REMOTE_COMMAND] alsabat -Phw:sofsoundwire,0 --standalone -n 240000 -r 48000 -c 2 -f S16_LE -F 821 -k 2.1
2024-01-28 22:11:42 UTC [REMOTE_COMMAND] alsabat -Chw:CODEC,0 -c 2 -r 48000 -f S16_LE -F 821 -k 2.1
Underrun: Broken pipe(-32)
Underrun: Broken pipe(-32)
Underrun: Broken pipe(-32)
Underrun: Broken pipe(-32)
We still see the underruns on certain DUT configurations.
Describe the bug The JD issue has been fixed on LNL-SDW platforms, so now we are able to check the audio quality on LNL-SDW. Now I observed the audio glitches on both playback and capture, but the reproduction rate is low, not easy to reproduce manually. Here are the failures we captured in CI daily test.
On playback: There're a lot of xrun warning during the test.
On capture:
To Reproduce
Playback test:~/sof-test/test-case/check-alsabat.sh -p hw:sofsoundwire,0 -c hw:CODEC,0 -C 2 -F 821
Capture test:~/sof-test/test-case/check-alsabat.sh -c hw:sofsoundwire,1 -p hw:CODEC,0 -C 2 -F 821
Reproduction Rate Low, less than 10%.
Environment 1) Branch name and commit hash of the 2 repositories: sof (firmware/topology) and linux (kernel driver).
wav-file.gz
cc: