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

[Richard Purdie]

On Sat, 2011-09-10 at 10:32 -0600, Gary Thomas wrote:
> On 2011-09-10 10:28, Richard Purdie wrote:
> > On Sat, 2011-09-10 at 09:21 -0600, Gary Thomas wrote:
> >> On 2011-09-10 07:13, Gary Thomas wrote:
> >>> 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.
> >>>
> >>
> >> Actually, I forgot that qemux86 also uses i586 packages, so there were quite a
> >> few other packages changed since Aug 31.  You can see the lists at
> >>     http://www.mlbassoc.com/poky/qemux86-rpms
> >>
> >
> > I've just tested qemux86 and qemuarm images and both of these were fine
> > (apart from pango issues which I locally reverted the change in question
> > for). I'm a little puzzled why things are therefore failing for people
> > but I would like to get to the bottom of it...
> 
> To be clear, I updated master to 98c2da694ca4c72b3e222a593b8baddea102bde5 and rebuilt
> my image (yesterday).  This image now crashes as reported.
> 
> What can I look at to help?

Can you test whether disabling prelinking removes the segfault?

We have a bug tracking this issue now:

http://bugzilla.yoctoproject.org/show_bug.cgi?id=1473

and believe that its only 32 bit build systems that have this issue.

Cheers,

Richard