-
Notifications
You must be signed in to change notification settings - Fork 349
Closed
Labels
LNLApplies to Lunar Lake platformApplies to Lunar Lake platformMTLApplies to Meteor Lake platformApplies to Meteor Lake platformP2Critical bugs or normal featuresCritical bugs or normal featuresbugSomething isn't working as expectedSomething isn't working as expected
Description
Describe the bug
This issue happens when checking the multiple-pause/resume case, it shows "pause resume PID **** had non-zero exit status" in console log, but there's no error in kernel log or mtrace. The reproduction rate is low about 20%. This issue can be reproduced on both MTL and LNL NOCODEC platforms.
Inner test ID:
LNLM_RVP_NOCODEC: 37146
MTLP_RVP_NOCODEC: 37016
To Reproduce
~/sof-test/test-case/multiple-pause-resume.sh -r 50
Reproduction Rate
20%
Environment
- Branch name and commit hash of the 2 repositories: sof (firmware/topology) and linux (kernel driver).
- Kernel: {0ba5acc6d6e4}
- SOF: {16b53b423c75}
- Name of the topology file
- Topology: {sof-lnl-nocodec.tplg and sof-mtl-nocodec.tplg}
- Name of the platform(s) on which the bug is observed.
- Platform: {LNL-NOCODEC and MTL-NOCODEC}
Screenshots or console output
=== PAUSE ===
(50/50) pcm'Port1' cmd'aplay' id'9': Wait for 32 ms before resume
2024-01-21 23:46:26 UTC [REMOTE_INFO] pipeline: Deepbuffer Port0 with aplay
2024-01-21 23:46:26 UTC [REMOTE_INFO] pipeline: Port1 with aplay
2024-01-21 23:46:26 UTC [REMOTE_INFO] Check expect exit status
declare -- cmd="journalctl_cmd --since=@1705880315"
2024-01-21 23:46:26 UTC [REMOTE_ERROR] pause resume PID 65117 had non-zero exit status
2024-01-21 23:46:26 UTC [REMOTE_INFO] Starting func_exit_handler(1)
Metadata
Metadata
Assignees
Labels
LNLApplies to Lunar Lake platformApplies to Lunar Lake platformMTLApplies to Meteor Lake platformApplies to Meteor Lake platformP2Critical bugs or normal featuresCritical bugs or normal featuresbugSomething isn't working as expectedSomething isn't working as expected