Git rev: master/6f0c5537e02c59e1c8f3b08f598dc049ff8ee098 Steps: Build kernel for qemumips or qemumips64: $ bitbake linux-yocto Check the kernel image in tmp/deploy directory: ###################################### $ ls vmlinux* vmlinux vmlinux.bin vmlinux--4.4.13+git0+870134f4bf_b1f51ad1d4-r0-qemumips-20160622143250.bin vmlinux.bin--4.4.13+git0+870134f4bf_b1f51ad1d4-r0-qemumips-20160622143250.bin vmlinux-qemumips.bin vmlinux.bin-qemumips.bin ####################################### Looks like there are 2 kernel images: vmlinux--4.4.13+git0+870134f4bf_b1f51ad1d4-r0-qemumips-20160622143250.bin and vmlinux.bin--4.4.13+git0+870134f4bf_b1f51ad1d4-r0-qemumips-20160622143250.bin. The first one is the real kernel image: $ file vmlinux--4.4.13+git0+870134f4bf_b1f51ad1d4-r0-qemumips-20160622143250.bin vmlinux--4.4.13+git0+870134f4bf_b1f51ad1d4-r0-qemumips-20160622143250.bin: ELF 32-bit MSB executable, MIPS, MIPS32 version 1 (SYSV), statically linked, BuildID[sha1]=73c8d754c24a7fb75394312646190bdf3aee7a74, not stripped But the latter one is not a kernel image: $ file vmlinux.bin--4.4.13+git0+870134f4bf_b1f51ad1d4-r0-qemumips-20160622143250.bin vmlinux.bin--4.4.13+git0+870134f4bf_b1f51ad1d4-r0-qemumips-20160622143250.bin: data This issue also happens on qemumips64.
This issue still happens on 2.2 M2 RC1 build Git rev: master/36feb38045b7a2af86ece147fec54b0db3bf491f
Moving to M3. It is unlikely I'll have cycles to look into this .. so if someone else wants to grab it, that would be excellent.
Still no cycles. moving to m4.
Zhe, Please check if this is a problem for master.
Yi, Does this still happen?