hijack.sh: make late logger config changes to nudge stuck DMA traces #663
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