Bug 8143 - qemu cpu kick thread on nightly-rpm when running sanity tests
Summary: qemu cpu kick thread on nightly-rpm when running sanity tests
Status: VERIFIED FIXED
Alias: None
Product: Build Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 1.9
Hardware: x86 x86
: Medium+ normal
Target Milestone: 1.9 M3
Assignee: Aníbal Limón
QA Contact: Daniel Istrate
URL:
Whiteboard:
: 8241 (view as bug list)
Depends on:
Blocks: 8176
  Show dependency tree
 
Reported: 2015-08-10 22:41 UTC by Alex Franco
Modified: 2015-10-06 08:44 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments
results of nightly-rpm build 418 (6.38 KB, text/plain)
2015-08-10 22:41 UTC, Alex Franco
no flags Details
Results of nightly-rpm build 494 (8.39 KB, text/plain)
2015-10-06 08:44 UTC, Daniel Istrate
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Franco 2015-08-10 22:41:35 UTC
Created attachment 2656 [details]
results of nightly-rpm build 418

qemu:qemu_cpu_kick_thread when booting image for do_testimage task

Builder: nightly-rpm
Build: 418
Buildslave: fedora21.osl.yoctoproject.org
Failed task: do_testimage
URL: https://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/418/steps/Running%20Sanity%20Tests/logs/stdio/text
See atttachment [1]

Relevant log section:

| stty: standard input: Inappropriate ioctl for device
| Acquiring lockfile for tap0...
| Using preconfigured tap device 'tap0'
| If this is not intended, touch /tmp/qemu-tap-locks/tap0.skip to make runqemu skip tap0.
| Running qemu-system-i386...
| /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-rpm/build/build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-i386 -kernel /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-rpm/build/build/tmp/deploy/images/qemux86/bzImage-qemux86.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=no,downscript=no -cpu qemu32 -drive file=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-rpm/build/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/testimage/core-image-minimal-qemux86-testimage.ext4,if=ide,format=raw -show-cursor -usb -usbdevice wacom-tablet -vga vmware -no-reboot -serial tcp:127.0.0.1:58773 -m 256 --append "vga=0 uvesafb.mode_option=640x480-32 root=/dev/hda rw mem=256M ip=192.168.7.2::192.168.7.1:255.255.255.0 oprofile.timer=1 rootfstype=ext4 console=tty1 console=ttyS0,115200n8"
| qemu:qemu_cpu_kick_thread: No such processReleasing lockfile of preconfigured tap device 'tap0'
| stty: standard input: Inappropriate ioctl for device
| stty: standard input: Inappropriate ioctl for device
| 
| DEBUG: Python function do_testimage finished
| ERROR: Function failed: core-image-minimal - FAILED to start qemu - check the task log and the boot log
NOTE: recipe core-image-minimal-1.0-r0: task do_testimage: Failed
ERROR: Task 0 (/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-rpm/build/meta/recipes-core/images/core-image-minimal.bb, do_testimage) failed with exit code '1'
Comment 1 Aníbal Limón 2015-08-12 20:39:56 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
Comment 2 Mariano Lopez 2015-08-12 21:03:04 UTC
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
Comment 3 Richard Purdie 2015-08-31 08:03:29 UTC
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.
Comment 4 Aníbal Limón 2015-08-31 19:00:45 UTC
(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.
Comment 7 Richard Purdie 2015-09-15 09:28:27 UTC
*** Bug 8241 has been marked as a duplicate of this bug. ***
Comment 8 Daniel Istrate 2015-10-06 08:42:10 UTC
Verified on master: eac61f37e36099f74485dab398b57f3812826d17
Comment 9 Daniel Istrate 2015-10-06 08:44:54 UTC
Created attachment 2783 [details]
Results of nightly-rpm build 494