From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: kernel panic when boot core-image-sato-sdk for qemux86
Date: Sat, 10 Sep 2011 17:28:45 +0100 [thread overview]
Message-ID: <1315672125.1986.30.camel@ted> (raw)
In-Reply-To: <4E6B806E.3020202@mlbassoc.com>
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@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...
Cheers,
Richard
next prev parent reply other threads:[~2011-09-10 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 23:09 kernel panic when boot core-image-sato-sdk for qemux86 Zhang, Jessica
2011-09-10 3:58 ` Bruce Ashfield
2011-09-12 21:57 ` Saul Wold
2011-09-13 4:37 ` Zhang, Jessica
2011-09-10 13:13 ` Gary Thomas
2011-09-10 15:21 ` Gary Thomas
2011-09-10 16:28 ` Richard Purdie [this message]
2011-09-10 16:32 ` Gary Thomas
2011-09-13 17:10 ` Richard Purdie
2011-09-13 18:11 ` Gary Thomas
2011-09-10 23:58 ` Zhang, Jessica
2011-09-11 2:19 ` Bruce Ashfield
2011-09-11 6:24 ` Zhang, Jessica
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1315672125.1986.30.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.