On 29 May 2018 at 15:01, Chris Redpath chris.redpath@arm.com wrote:
Hi Leo,
On 17/05/18 10:12, Leo Yan wrote:
Hi all,
I can reproduce the warning from WALT function walt_fixup_busy_time() in Android kernel 4.14 on Hikey960 board.
The detailed log is as below. To trigger this issue, I usually reboot the board for multiple times: 'while true; do adb reboot; sleep 30; done' and at the boot time this issue can be reproduced.
Before dig into this, I share the log to check in case we have the fixing yet for it.
I have seen this occasionally too and I'm suspicious that there is something wrong with Walt in android-4.14, seeing the comments I added about the lock problems.
It looks to me like we have a clock sync problem, I'm guessing you can't switch on tracing in time to catch it so we can see how the Walt signal is being built?
AFAIK, trace can be enable at boot time with command line parameter if needed
--Chris
Thanks,
Leo Yan
[ removed log ]
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
eas-dev mailing list eas-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/eas-dev