[yocto] kernel panic when boot core-image-sato-sdk for qemux86

Gary Thomas gary at mlbassoc.com
Sat Sep 10 06:13:40 PDT 2011


On 2011-09-09 17:09, Zhang, Jessica wrote:
> Hi,
>
> Has anybody ran into kernel panic when boot up core-image-sato-sdk for qemux86. I’ve been having this issue with several clean build for two days. And my latest build tree is a
> freshly cloned tree against poky-master with commit:
>
> commit 20dbf0024385eaef61a04d8773fd7640e3c8cc6d
>
> Author: Richard Purdie <richard.purdie at linuxfoundation.org>
>
> Date: Fri Sep 9 19:07:40 2011 +0100
>
> The qemu kernel panic messages are:
>
> INIT: version 2.88 booting
>
> Init[1]: segfault at 38 ip 495076c7 sp bfd9b60c error 4 in libc-2.13.so[49492000+15f000]
>
> Init[1]: segfault at 16 ip 0804b3c7 sp bfd9b280 error 4 in init.sysvinit[8048000+7000]
>
> Kernel panic – not syncing: Attempted to kill init!
>
> Pid: 1, comm: init Not tainted 3.0.4-yocto-standard+ #1

Verified - fails for me here as well.  A Bruce said, a build from just a few days
ago did work.  Note: I only tried core-image-sato

As far as I can tell, the only packages that were rebuilt since my last go on
Aug 31 were virtual/kernel & perf

Looks like it's something to do with kernel changes.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



More information about the yocto mailing list