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

[Zhang, Jessica]

Bruce,

Even though I haven't test utrace, I just tested my newly built sato-sdk with the same tree for arm and didn't run into kernel panic.  So seems not related to utrace and more specific to x86.

Thanks,
Jessica

-----Original Message-----
From: yocto-bounces at yoctoproject.org [mailto:yocto-bounces at yoctoproject.org] On Behalf Of Bruce Ashfield
Sent: Saturday, September 10, 2011 7:20 PM
To: Richard Purdie
Cc: yocto at yoctoproject.org
Subject: Re: [yocto] kernel panic when boot core-image-sato-sdk for qemux86

On 11-09-10 12:28 PM, 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...

As would I! I just audited the kernel changes, and there's nothing that
should cause anything so severe. My build and boot of course worked as
well.

The grand total of changes since the 3.0.4 update are:

   3c9ebee meta: re-enable utrace feature for linux-yocto
   82140b9 meta: re-enable systemtap feature for linux-yocto
   258af0b meta: update kver to v3.0.4

And both of those were merged and boot tested a while ago.

And the reports of different results from the autobuilder to local machines.
Really makes me wonder about what's really being built and if
something strange is being fetched.

Jessica/Gary: if you explicitly disable utrace, I wonder if that
makes a difference, since it's the only change that should even
have a chance to cause runtime issues. (to disable it, just toss
a config frag with "# CONFIG_UTRACE is not set" and build, or just
confirm that it is off via menuconfig).

Cheers,

Bruce


>
> Cheers,
>
> Richard
>
>
>
>
>
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

_______________________________________________
yocto mailing list
yocto at yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto