| Summary: | qemu cpu kick thread on nightly-rpm when running sanity tests | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [QA/Testing] Build Testing | Reporter: | Alex Franco <alejandro.franco> | ||||||
| Component: | general | Assignee: | Aníbal Limón <anibal.limon> | ||||||
| Status: | VERIFIED FIXED | QA Contact: | Daniel Istrate <daniel.alexandrux.istrate> | ||||||
| Severity: | normal | ||||||||
| Priority: | Medium+ | CC: | alexandru.c.georgescu, anibal.limon, jku, mariano.lopez, richard.purdie | ||||||
| Version: | 1.9 | ||||||||
| Target Milestone: | 1.9 M3 | ||||||||
| Hardware: | x86 | ||||||||
| OS: | x86 | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | Don't know | |||||||
| Bug Depends on: | |||||||||
| Bug Blocks: | 8176 | ||||||||
| Attachments: |
|
||||||||
|
Description
Alex Franco
2015-08-10 22:41:35 UTC
I wrote a patch to get information about the status of qemu cpu and backtrace, Now in reviewing at, http://lists.openembedded.org/pipermail/openembedded-core/2015-August/108728.html The search for "cpu_kick_thread" in the error reporting system shows 9 errors and the oldest is from 2015-05-13. There is not a direct correlation with MACHINE types or qemu versions. MACHINE types:qemuarm, qemuarm64, qemumips64, qemuppc, qemux86, qemux86-64 qemu versions: 2.3.0, 2.4.0-rc0, 2.4.0-rc3 The link for the error reporting systems is: http://errors.yoctoproject.org/Errors/Search/?query=qemu_cpu_kick_thread Taking the address info from https://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/480/steps/Running%20Sanity%20Tests/logs/stdio and playing with "DISPLAY=:1 gdb -s qemu-system-i386 -e ../../../../../../sysroots/x86_64-linux/usr/bin/qemu-system-i386" (gdb) info symbol 0xa09df backtrace_print + 45 in section .text (gdb) info symbol 0xcf2a4 qemu_cpu_kick_thread + 132 in section .text (gdb) info symbol 0xd08a8 qemu_mutex_lock_iothread + 152 in section .text (gdb) info symbol 0x344883 call_rcu_thread + 259 in section .text which at least gives us an idea of the function path that failed. (In reply to comment #3) > Taking the address info from > https://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/480/ > steps/Running%20Sanity%20Tests/logs/stdio and playing with "DISPLAY=:1 gdb > -s qemu-system-i386 -e > ../../../../../../sysroots/x86_64-linux/usr/bin/qemu-system-i386" > > (gdb) info symbol 0xa09df > backtrace_print + 45 in section .text > (gdb) info symbol 0xcf2a4 > qemu_cpu_kick_thread + 132 in section .text > (gdb) info symbol 0xd08a8 > qemu_mutex_lock_iothread + 152 in section .text > (gdb) info symbol 0x344883 > call_rcu_thread + 259 in section .text > > which at least gives us an idea of the function path that failed. I found a commit related to this error, http://git.qemu.org/?p=qemu.git;a=commit;h=a59629fcc6f603e19b516dc08f75334e5c480bd0 Seems to be and sync problem in initialization. Merged at, http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ea3384e9f84388d60331ba24f67ce5716ce45ee0 *** Bug 8241 has been marked as a duplicate of this bug. *** Verified on master: eac61f37e36099f74485dab398b57f3812826d17 Created attachment 2783 [details]
Results of nightly-rpm build 494
|