3335 2012-10-25 14:34:00 +0000 Shutdown is handing on qemuarm 2012-10-25 14:56:37 +0000 1 1 11 Runtime General Runtime General Runtime 1.2.1 x86 arm RESOLVED DUPLICATE 684 Undecided normal --- 1 venkatarg sgw --- --- --- oldest_to_newest 26902 0 venkatarg 2012-10-25 14:34:00 +0000 "shutdown -h now" Qemu is hanging while shutdown Filesystem: core-image-sato-sdk-qemuarm.ext3,core-image-sato-qemuarm.ext3 core-image-sato-sdk-qemux86-64.tar.bz2(nfs) Arch: Arm buildtaken from : http://autobuilder.yoctoproject.org/pub/nightly/20121018-4/machines/qemu/qemuarm/ Log: runqemu qemuarm /home/yocto/Yocto-builds-test/20121018-4/zImage-qemuarm.bin /home/yocto/Yocto-builds-test/20121018-4/core-image-sato-sdk-qemuarm.ext3 Continuing with the following parameters: KERNEL: [/home/yocto/Yocto-builds-test/20121018-4/zImage-qemuarm.bin] ROOTFS: [/home/yocto/Yocto-builds-test/20121018-4/core-image-sato-sdk-qemuarm.ext3] FSTYPE: [ext3] Setting up tap interface under sudo Acquiring lockfile for tap0... WARNING: distccd not present, no distcc support loaded. Running qemu-system-arm... /opt/poky/1.2.1/sysroots/i686-pokysdk-linux/usr/bin/qemu-system-arm -kernel /home/yocto/Yocto-builds-test/20121018-4/zImage-qemuarm.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=no,downscript=no -M versatilepb -hda /home/yocto/Yocto-builds-test/20121018-4/core-image-sato-sdk-qemuarm.ext3 -no-reboot -show-cursor -usb -usbdevice wacom-tablet -no-reboot -m 128 --append "root=/dev/sda rw console=ttyAMA0,115200 console=tty ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=128M highres=off " Then 1. Qemu UI Successfully came up 2. executed "shutdown -h now" 3. Hanged when processing bar shown complete. 4. Given Ctrl+c in lauch terminal, contd... qemu: terminating on signal 2 root's password: root's password: Set 'tap0' nonpersistent Releasing lockfile of preconfigured tap device 'tap0' Set 'tap0' nonpersistent Releasing lockfile of preconfigured tap device 'tap0' 26907 1 sgw 2012-10-25 14:56:37 +0000 This is a known issue with the kernel *** This bug has been marked as a duplicate of bug 684 ***