hijack.sh: make late logger config changes to nudge stuck DMA traces #663
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There are bugs that cause DMA drops and the last few lines to get stuck somewhere. Changing the logger configuration and waiting for 1 second seems to be enough to nudge the system and force it to DMA a bit more logs: hopefully all the logs relevant to the current test. Running this logger configuration command twice makes it very easy to observe the stuck lines bug: the "ipc" logs corresponding to this -F command will appear _only once_ at the end of the slogger.txt DMA trace! Signed-off-by: Marc Herbert <marc.herbert@intel.com>
Collaborator
Author
|
https://sof-ci.01.org/softestpr/PR663/build673/devicetest failed on BYT because it has no "tone" component. The tests timed out because they aborted before printing PASS or FAIL. Both issues should be addressed on v2 just forced-pushed. Some tests did not fail on BYT, most likely because they don't have Sampling a few other slogger outputs in build673 shows the desired effect is achieved. |
marc-hb
requested review from
aiChaoSONG,
andyross,
cujomalainey,
fredoh9,
keqiaozhang,
keyonjie,
ktrzcinx,
kv2019i,
lgirdwood,
lyakh,
mmaka1,
plbossart and
ranj063
Collaborator
Author
|
https://sof-ci.01.org/softestpr/PR663/build674/devicetest/ is all green. Looking at a few random slogger outputs shows that the logs are slightly incomplete as explained in the code comments. |
This was referenced Apr 23, 2021
aiChaoSONG
approved these changes
Jun 7, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are bugs that cause DMA drops and the last few lines to get stuck
somewhere. Changing the logger configuration and waiting for 1 second
seems to be enough to nudge the system and force it to DMA a bit more
logs: hopefully all the logs relevant to the current test.
Running this logger configuration command twice makes it very easy to
observe the stuck lines bug: the "ipc" logs corresponding to this -F
command will appear only once at the end of the slogger.txt DMA trace!
Signed-off-by: Marc Herbert marc.herbert@intel.com