-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG][MTL-005.0.3] ipc timedout on killing speaker pipeline aplay #8028
Comments
probably missing a kernel PR to fix that part |
Unfortunately, this happens in Fedora with sof-dev + mtl-005.0.3 firmware, while firmware is configured with Despite the value of CONFIG_ADSP_IMR_CONTEXT_SAVE(yes or no), if apply #8007, the issue will disapprear. |
Issue cannot be reproduced with sof-dev kernel + firmware latest main branch (commit fb6c3b7, IMR context save already enabled) + PR #8019 @abonislawski |
Status: Waits for #8019 merge |
@aiChaoSONG @abonislawski @lrudyX The Linux workaround PR thesofproject/linux#4531? applied in upstream: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=26ef47e5ba600ead306ee19e0bf56c1bf59213a3 This will give us more time on final FW fix. |
@aiChaoSONG does the issue also occur on main, or on MTL_006? |
It is not easy to reproduce the issue as before(mtl005.0.3) with MTL6.2 release. I see another issue(some issue rander is fixing I think thesofproject/linux#4832) before I could reproduce this one.
|
This issue cannot be reproduced on latest main branch. Let's track the new issue in #7990. Closing this bug. |
Describe the bug
Doing playback to speaker pipeline, and kill the process with CTRL+C. sometimes there will be ipc timed out in the kernel message. And there is no obvious error message in mtrace.
On issue happened, we are not able to do playback/capture anymore.
To Reproduce
aplay -Dhw:0,2 -f dat -i -vvv chao/California_Dreaming.wav
Reproduction Rate
1/5
Environment
speaker_dmesg.txt
speaker_mtrace.txt
With patch #8007, issue is not reproducable.
Similar issue may be the same root cause: #7990
The text was updated successfully, but these errors were encountered: