Hi, On Fri, Jan 20, 2023 at 04:44:36PM +0200, Mikko Rapeli via lists.openembedded.org wrote: > I get a qemu hang on kirkstone, swtpm and optee. One of the > optee-test/xtest hangs the qemu machine in some kind of deadlock. > While this needs to be debugged and tested, the oeqa runtime tests > also hanged and never returned. Thus this patch set. With these changes > qemu deadlock is detected and with do_testimage() task eventually exits > with all correct tests failing and the hangin qemu system killed. > There are a lot of debug prints added by this patch set but I don't of > any other way to debug complex python code. strace output from the hang > doesn't tell where the deadlock happened.
On #yocto Richard said he doesn't like the large amount of debug prints here. If there are some specific ones I should drop, then please let me know. I think the logs in do_testimage() are quite readable with these enabled. I can follow the logs and see target debug output in larger, multi line chunks. I can see if an ssh command on target is waiting for output for a long time, and output of the commands comes in larger clear chunks. I have a complex boot sequence which includes firmware, kernel, initramfs, rootfs encryption etc before entering login prompt so collecting all logs from the boot is criticial, and the boot takes a long time too so seeing frequent output in do_testimage() logs is also important. The chunk reading of output data really helps. Cheers, -Mikko
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#176341): https://lists.openembedded.org/g/openembedded-core/message/176341 Mute This Topic: https://lists.openembedded.org/mt/96401356/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
