hijack.sh: make late logger config changes to nudge stuck DMA traces

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>

Author: marc-hb

case-lib/hijack.sh

@@ -31,6 +31,21 @@ function func_exit_handler()
             sleep 1s
         }
 
+        # There are bugs that cause DMA drops and the last few lines to
+        # get stuck somewhere. This hack 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.
+        for i in 1 2; do
+            # Running this 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!
+            sudo "$SOFLOGGER" -l "$(find_ldc_file)" -F info=tone > /dev/null
+        done
+        # We _also_ need to wait for the trace_work() thread to run;
+        # BOTH are needed. The bug is not just a delay.
+        sleep 1
+
         local loggerBin wcLog; loggerBin=$(basename "$SOFLOGGER")
         # We need this to avoid the confusion of a "Terminated" message
         # without context.