-
Notifications
You must be signed in to change notification settings - Fork 314
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] TGLU_RVP_NOCODEC IPC timed out for PIPE_FREE when multiple-pipeline-all #5103
Comments
@lgirdwood, in case of IPC timeout we don't have stack trace available. The stack can be only shown if we have firmware panic or assert. |
@ujfalusi should we see it here as the log says we have a FW exception ?
|
This is printed from I guess the idea is that this could be called from different places (it is not) and be a generic "exception" printer. The problem is that if we don't have a panic then we don't have callstack. The callstack is only prepared and given when the firmware panics/asserts. I'll try to come up with a better expression for this and re-word it. The IPC timeout might or might not be fatal. In case it is fatal we are going to have a panic as well, which will print the stack. "Firmware timeout" is a good candidate ;) |
This error is potentially caused by unsafe BUFFER_FREE. Fix for this in in review at #5635 |
Now merged, can you retest. Thanks ! |
This issue no longer recurs. |
Describe the bug
In inner test ID 8954, model=TGLU_RVP_NOCODEC, testcase=multiple-pipeline-all-50,
When running all pipelines in parallel on TGLU_RVP_NOCODEC, IPC timed out for PIPE_FREE.
To Reproduce
TPLG=/lib/firmware/intel/sof-tplg/sof-tgl-nocodec.tplg MODEL=TGLU_RVP_NOCODEC ~/sof-test/test-case/multiple-pipeline.sh -f p -c 20 -l 150
Reproduction Rate
Around 1/150 in manual reproduction.
Environment
Kernel Branch: topic/sof-dev
Kernel Commit: thesofproject/linux@9e5edeba
SOF Branch: main
SOF Commit: afac44af5f49
Topology:/lib/firmware/intel/sof-tplg/sof-tgl-nocodec.tplg
Platform: TGLU_RVP_NOCODEC
Screenshots or console output
dmesg
The text was updated successfully, but these errors were encountered: