From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 00/14] oeqa runtime tests when qemu hangs
Date: Wed, 25 Jan 2023 09:54:11 +0200 [thread overview]
Message-ID: <Y9DgI+HyBTGNmiFa@nuoska> (raw)
In-Reply-To: <173C0B9603DBAB46.24231@lists.openembedded.org>
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
next parent reply other threads:[~2023-01-25 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <173C0B9603DBAB46.24231@lists.openembedded.org>
2023-01-25 7:54 ` Mikko Rapeli [this message]
2023-01-25 8:03 ` [OE-core] [PATCH 00/14] oeqa runtime tests when qemu hangs Alexander Kanavin
2023-01-25 12:32 ` Mikko Rapeli
2023-01-25 21:10 ` Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y9DgI+HyBTGNmiFa@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox