-
Notifications
You must be signed in to change notification settings - Fork 318
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] Zephyr "mtrace" logs empty until the next reboot #9087
Comments
Last passing test:
The 7 tests that ran after this all had an empty They did not seem to fail for any other reason, everything else seems fine. I haven't found any error or anything suspicious in any log; journalctl included. Anything specific one should be looking for? Some particular IPC? No other device in the same run experienced anything similar and I haven't seen anything like this ever before. There was apparently no "loose" mtrace-reader.py because mtrace.txt would not be empty in that case, it would have the error message described in: This does not look like thesofproject/sof-test#1109 for the same reason: no error message? After CI rebooted that device, mtrace seemed to work perfectly fine for the rest of the test run, see above. Note the DSP "restores" from IMR on this system, it's not booting from scratch from D3. |
Just happened again on
No other obvious error in the logs. Final mtrace logs (from the previous test) copied below. Note the multiple "messages dropped" warnings. Again this is a system with "IMR restore" mtrace worked again after a complete Linux reboot.
|
Observed again in daily test run 41268?model=MTLP_RVP_NOCODEC&testcase=test-speaker |
and again in daily 42634?model=MTLP_RVP_SDW&testcase=check-alsabat-headset-playback-599 |
In this LNL example we lost BOTH mtrace and kernel logs: |
No owner -> v2.12 |
Describe the bug
Zephyr "mtrace" logs have become suddenly and silently empty until the next reboot.
This happened in daily test 40387
To Reproduce
Could not reproduce.
Reproduction Rate
Seen only once for now.About 1/100 timesExpected behavior
Firmware logs are not totally empty.
Impact
No firmware logs
Environment
jf-mtlp-rvp-nocodec-5. Daily test 40387
Start Time: 2024-04-26 14:07:35 UTC
End Time: 2024-04-26 17:23:17 UTC
Linux Branch: topic/sof-dev
Linux Commit: f084b17039d5
KConfig Branch: master
KConfig Commit: a63502374811
SOF Commit: 278ecc5b74ad
Zephyr Commit: 24554363379d
Screenshots or console output
cc:
The text was updated successfully, but these errors were encountered: