[Buildroot] Kernel panic!

[Buildroot] Kernel panic!

[Peter Korsgaard]

>>>>> "Mahanteshwari" == Mahanteshwari Hiremath <Mahanteshwari.Hiremath@lnties.com> writes:

 Mahanteshwari> Hi,

 Mahanteshwari>     I am trying use buildroot built root file system for
 Mahanteshwari>  my embedded target board. I am able to boot my system
 Mahanteshwari>  partially, it stops at some point saying /sbin/init:
 Mahanteshwari>  cannot load libc.so.0, kernel panic-not
 Mahanteshwari>  syncing:Attempted to kill init

Buildroot related questions should go to the buildroot list (addressed
in this mail). Please reply (only to the buildroot list) with more
details about your system, E.G. your hw platform and your buildroot
version and configuration (run make savedefconfig and send the defconfig
file).

Thanks.

-- 
Bye, Peter Korsgaard

[Buildroot] Kernel panic!

[Mahanteshwari Hiremath]

Hi,
        below is the defconfig file contents, buildroot version "buildroot-2011.08 ", hardware platform- X86(PPM-GX500,GEODE)


R2_x86_geode=y
BR2_HOST_DIR="$(BASE_DIR)/staging"
BR2_DEPRECATED=y
BR2_HAVE_DEVFILES=y
BR2_KERNEL_HEADERS_2_6_39=y
# BR2_GCC_SHARED_LIBGCC is not set
BR2_TOOLCHAIN_BUILDROOT_LARGEFILE=y
BR2_TOOLCHAIN_BUILDROOT_LOCALE=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_PTHREADS_OLD=y
BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y
BR2_PACKAGE_GCC_TARGET=y
BR2_PACKAGE_MAKE=y
BR2_PACKAGE_QT=y
BR2_PACKAGE_QT_LICENSE_APPROVED=y
BR2_PACKAGE_QT_QT3SUPPORT=y
BR2_PACKAGE_QT_MOUSE_PC=y
BR2_PACKAGE_QT_KEYBOARD_LINUXINPUT=y
BR2_PACKAGE_OPENSSL=y
BR2_PACKAGE_FONTCONFIG=y
BR2_PACKAGE_LIBPNG=y
BR2_PACKAGE_PIXMAN=y
BR2_PACKAGE_SYSVINIT=y
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="/home/.config"




Regards,
Mahanteshwari Hiremath.


Larsen & Toubro Limited

www.larsentoubro.com

This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

[Buildroot] Kernel panic!

[Mahanteshwari Hiremath]

Hi ,
    I am trying use buildroot built root file system for my embedded target board. I am able to boot my system partially, it stops at some point saying
 /sbin/init: cannot load libc.so.0, kernel panic-not syncing:Attempted to kill init

I tried hard to solve this, but unable to fix this error(I don't have any understanding about buildroot code).

I want my embedded board to boot with buildroot rootfile sytem without any problem.



Regards,
Mahanteshwari Hiremath.


________________________________________
From: Peter Korsgaard [jacmet at gmail.com] on behalf of Peter Korsgaard [jacmet at sunsite.dk]
Sent: Tuesday, December 06, 2011 2:43 PM
To: Mahanteshwari Hiremath; buildroot at uclibc.org
Cc: uclibc at uclibc.org
Subject: Re: Kernel panic!

>>>>> "Mahanteshwari" == Mahanteshwari Hiremath <Mahanteshwari.Hiremath@lnties.com> writes:

 Mahanteshwari> Hi,

 Mahanteshwari>     I am trying use buildroot built root file system for
 Mahanteshwari>  my embedded target board. I am able to boot my system
 Mahanteshwari>  partially, it stops at some point saying /sbin/init:
 Mahanteshwari>  cannot load libc.so.0, kernel panic-not
 Mahanteshwari>  syncing:Attempted to kill init

Buildroot related questions should go to the buildroot list (addressed
in this mail). Please reply (only to the buildroot list) with more
details about your system, E.G. your hw platform and your buildroot
version and configuration (run make savedefconfig and send the defconfig
file).

Thanks.

--
Bye, Peter Korsgaard


****************************************************************


Hi,
        below is the defconfig file contents, buildroot version "buildroot-2011.08 ", hardware platform- X86(PPM-GX500,GEODE)


R2_x86_geode=y
BR2_HOST_DIR="$(BASE_DIR)/staging"
BR2_DEPRECATED=y
BR2_HAVE_DEVFILES=y
BR2_KERNEL_HEADERS_2_6_39=y
# BR2_GCC_SHARED_LIBGCC is not set
BR2_TOOLCHAIN_BUILDROOT_LARGEFILE=y
BR2_TOOLCHAIN_BUILDROOT_LOCALE=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_PTHREADS_OLD=y
BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y
BR2_PACKAGE_GCC_TARGET=y
BR2_PACKAGE_MAKE=y
BR2_PACKAGE_QT=y
BR2_PACKAGE_QT_LICENSE_APPROVED=y
BR2_PACKAGE_QT_QT3SUPPORT=y
BR2_PACKAGE_QT_MOUSE_PC=y
BR2_PACKAGE_QT_KEYBOARD_LINUXINPUT=y
BR2_PACKAGE_OPENSSL=y
BR2_PACKAGE_FONTCONFIG=y
BR2_PACKAGE_LIBPNG=y
BR2_PACKAGE_PIXMAN=y
BR2_PACKAGE_SYSVINIT=y
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="/home/.config"




Regards,
Mahanteshwari Hiremath.




Larsen & Toubro Limited

www.larsentoubro.com

This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

[Buildroot] Kernel Panic .....

[Robin Mordasiewicz]

I am trying to boot the image as an initrd filesystem over pxe, but I see 
an error
'Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers'

in my pxelinux.cfg/default

label test
   kernel linux-kernel-2.6.19.1-i386
   append ramdisk_blocksize=4096 initrd=rootfs.i386.ext2 root=/dev/ram0 ramdisk_size=524288

Is there anything I am required to change to make this kernel and image 
work over booting from pxe ?

[Buildroot] Kernel Panic .....

[Robin Mordasiewicz]

On Tue, 19 Dec 2006, Robin Mordasiewicz wrote:

> I am trying to boot the image as an initrd filesystem over pxe, but I see
> an error
> 'Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers'
>
> in my pxelinux.cfg/default
>
> label test
>   kernel linux-kernel-2.6.19.1-i386
>   append ramdisk_blocksize=4096 initrd=rootfs.i386.ext2 root=/dev/ram0 ramdisk_size=524288
>
> Is there anything I am required to change to make this kernel and image
> work over booting from pxe ?

I needed to build some RAM disk drivers into the kernel.

[Buildroot] Kernel Panic .....

[Joe Pruett]

On Tue, 19 Dec 2006, Robin Mordasiewicz wrote:

> On Tue, 19 Dec 2006, Robin Mordasiewicz wrote:
> 
> > I am trying to boot the image as an initrd filesystem over pxe, but I see
> > an error
> > 'Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers'
> >
> > in my pxelinux.cfg/default
> >
> > label test
> >   kernel linux-kernel-2.6.19.1-i386
> >   append ramdisk_blocksize=4096 initrd=rootfs.i386.ext2 root=/dev/ram0 ramdisk_size=524288
> >
> > Is there anything I am required to change to make this kernel and image
> > work over booting from pxe ?
> 
> I needed to build some RAM disk drivers into the kernel.

how exactly did you do that?  that is where i have finally gotten after 
making that kernel-patches directory (as you also just posted) and fixing 
the problem that grub no longer has a -19 version at debian.org (-20 seems 
to be working).  i made an iso image and ran into the same kernel panic 
because it seems to want a cpio image.  i have just rebuilt using the 
linux26.config file instead of busybox.config and will be booting in a few 
minutes to see how that goes...

[Buildroot] Kernel Panic .....

[Joe Pruett]

> > > I am trying to boot the image as an initrd filesystem over pxe, but I see
> > > an error
> > > 'Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers'
> > >
> > > in my pxelinux.cfg/default
> > >
> > > label test
> > >   kernel linux-kernel-2.6.19.1-i386
> > >   append ramdisk_blocksize=4096 initrd=rootfs.i386.ext2 root=/dev/ram0 ramdisk_size=524288
> > >
> > > Is there anything I am required to change to make this kernel and image
> > > work over booting from pxe ?
> > 
> > I needed to build some RAM disk drivers into the kernel.
> 
> how exactly did you do that?  that is where i have finally gotten after 
> making that kernel-patches directory (as you also just posted) and fixing 
> the problem that grub no longer has a -19 version at debian.org (-20 seems 
> to be working).  i made an iso image and ran into the same kernel panic 
> because it seems to want a cpio image.  i have just rebuilt using the 
> linux26.config file instead of busybox.config and will be booting in a few 
> minutes to see how that goes...

nope, the linux26.config doesn't seem to help.  so did you just go into 
the linux directory and 'make menuconfig' in there?  or some other magic?

[Buildroot] Kernel Panic .....

[Robin Mordasiewicz]

On Tue, 19 Dec 2006, Joe Pruett wrote:
> On Tue, 19 Dec 2006, Robin Mordasiewicz wrote:
>> On Tue, 19 Dec 2006, Robin Mordasiewicz wrote:
>>
>>> I am trying to boot the image as an initrd filesystem over pxe, but I see
>>> an error
>>> 'Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers'
>>>
>>> in my pxelinux.cfg/default
>>>
>>> label test
>>>   kernel linux-kernel-2.6.19.1-i386
>>>   append ramdisk_blocksize=4096 initrd=rootfs.i386.ext2 root=/dev/ram0 ramdisk_size=524288
>>>
>>> Is there anything I am required to change to make this kernel and image
>>> work over booting from pxe ?
>>
>> I needed to build some RAM disk drivers into the kernel.
>
> how exactly did you do that?  that is where i have finally gotten after
> making that kernel-patches directory (as you also just posted) and fixing
> the problem that grub no longer has a -19 version at debian.org (-20 seems
> to be working).  i made an iso image and ran into the same kernel panic
> because it seems to want a cpio image.  i have just rebuilt using the
> linux26.config file instead of busybox.config and will be booting in a few
> minutes to see how that goes...

Not sure if I am following you. I think you may be getting the kernel 
config and the busybox config confused. The documentation for customizing 
busybox does not mention modifying the kernel, but what I did to customize 
the kernel is something like the following.

cd build_i386/linux-2.6.19.1
cp .config .config.original
make mrproper
make menuconfig
(set the kernel options you require)
cd ../../
make

[Buildroot] Kernel Panic .....

[Bernhard Fischer]

On Tue, Dec 19, 2006 at 11:47:54PM -0500, Robin Mordasiewicz wrote:
>On Tue, 19 Dec 2006, Joe Pruett wrote:
>> On Tue, 19 Dec 2006, Robin Mordasiewicz wrote:
>>> On Tue, 19 Dec 2006, Robin Mordasiewicz wrote:
>>>
>>>> I am trying to boot the image as an initrd filesystem over pxe, but I see
>>>> an error
>>>> 'Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers'
>>>>
>>>> in my pxelinux.cfg/default
>>>>
>>>> label test
>>>>   kernel linux-kernel-2.6.19.1-i386
>>>>   append ramdisk_blocksize=4096 initrd=rootfs.i386.ext2 root=/dev/ram0 ramdisk_size=524288
>>>>
>>>> Is there anything I am required to change to make this kernel and image
>>>> work over booting from pxe ?
>>>
>>> I needed to build some RAM disk drivers into the kernel.
>>
>> how exactly did you do that?  that is where i have finally gotten after
>> making that kernel-patches directory (as you also just posted) and fixing
>> the problem that grub no longer has a -19 version at debian.org (-20 seems
>> to be working).  i made an iso image and ran into the same kernel panic
>> because it seems to want a cpio image.  i have just rebuilt using the
>> linux26.config file instead of busybox.config and will be booting in a few
>> minutes to see how that goes...
>
>Not sure if I am following you. I think you may be getting the kernel 
>config and the busybox config confused. The documentation for customizing 
>busybox does not mention modifying the kernel, but what I did to customize 
>the kernel is something like the following.
>
>cd build_i386/linux-2.6.19.1
>cp .config .config.original
>make mrproper
>make menuconfig
>(set the kernel options you require)
>cd ../../
>make

there is a make linux26-menuconfig target for that (for i386 with
the generic x86 target support option turned on, at least).

[Buildroot] Kernel Panic .....

[Joe Pruett]

On Wed, 20 Dec 2006, Bernhard Fischer wrote:

> On Tue, Dec 19, 2006 at 11:47:54PM -0500, Robin Mordasiewicz wrote:
> >On Tue, 19 Dec 2006, Joe Pruett wrote:
> >> On Tue, 19 Dec 2006, Robin Mordasiewicz wrote:
> >>> On Tue, 19 Dec 2006, Robin Mordasiewicz wrote:
> >>>
> >>>> I am trying to boot the image as an initrd filesystem over pxe, but I see
> >>>> an error
> >>>> 'Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers'
> >>>>
> >>>> in my pxelinux.cfg/default
> >>>>
> >>>> label test
> >>>>   kernel linux-kernel-2.6.19.1-i386
> >>>>   append ramdisk_blocksize=4096 initrd=rootfs.i386.ext2 root=/dev/ram0 ramdisk_size=524288
> >>>>
> >>>> Is there anything I am required to change to make this kernel and image
> >>>> work over booting from pxe ?
> >>>
> >>> I needed to build some RAM disk drivers into the kernel.
> >>
> >> how exactly did you do that?  that is where i have finally gotten after
> >> making that kernel-patches directory (as you also just posted) and fixing
> >> the problem that grub no longer has a -19 version at debian.org (-20 seems
> >> to be working).  i made an iso image and ran into the same kernel panic
> >> because it seems to want a cpio image.  i have just rebuilt using the
> >> linux26.config file instead of busybox.config and will be booting in a few
> >> minutes to see how that goes...
> >
> >Not sure if I am following you. I think you may be getting the kernel 
> >config and the busybox config confused. The documentation for customizing 
> >busybox does not mention modifying the kernel, but what I did to customize 
> >the kernel is something like the following.
> >
> >cd build_i386/linux-2.6.19.1
> >cp .config .config.original
> >make mrproper
> >make menuconfig
> >(set the kernel options you require)
> >cd ../../
> >make
> 
> there is a make linux26-menuconfig target for that (for i386 with
> the generic x86 target support option turned on, at least).
> 

ok, i determined that the missing piece is that the ramdisk block device 
needs to be set to compile in, not be a module.  to make an iso function, 
i also had to hack in a makefile entry for LINUX_KERNEL (i just set it to 
LINUX26_KERNEL).  after that things started working.  i also seem to see 
an ordering problem that if i made a kernel change, i had to run make 
twice in order for that to get into the iso.

i'm not sure where those two changes should be done officially, or i'd 
submit a patch.  it seems that if the iso relies on ramdisk support, then 
it makes sense to have that enabled by default, and the LINUX_KERNEL vs 
LINUX26_KERNEL make var should be addressed.  

[Buildroot] Kernel Panic .....

[Bernhard Fischer]

On Wed, Dec 20, 2006 at 09:19:32PM -0800, Joe Pruett wrote:
>On Wed, 20 Dec 2006, Bernhard Fischer wrote:
>
>> On Tue, Dec 19, 2006 at 11:47:54PM -0500, Robin Mordasiewicz wrote:
>> >On Tue, 19 Dec 2006, Joe Pruett wrote:
>> >> On Tue, 19 Dec 2006, Robin Mordasiewicz wrote:
>> >>> On Tue, 19 Dec 2006, Robin Mordasiewicz wrote:
>> >>>
>> >>>> I am trying to boot the image as an initrd filesystem over pxe, but I see
>> >>>> an error
>> >>>> 'Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers'
>> >>>>
>> >>>> in my pxelinux.cfg/default
>> >>>>
>> >>>> label test
>> >>>>   kernel linux-kernel-2.6.19.1-i386
>> >>>>   append ramdisk_blocksize=4096 initrd=rootfs.i386.ext2 root=/dev/ram0 ramdisk_size=524288
>> >>>>
>> >>>> Is there anything I am required to change to make this kernel and image
>> >>>> work over booting from pxe ?
>> >>>
>> >>> I needed to build some RAM disk drivers into the kernel.
>> >>
>> >> how exactly did you do that?  that is where i have finally gotten after
>> >> making that kernel-patches directory (as you also just posted) and fixing
>> >> the problem that grub no longer has a -19 version at debian.org (-20 seems
>> >> to be working).  i made an iso image and ran into the same kernel panic
>> >> because it seems to want a cpio image.  i have just rebuilt using the
>> >> linux26.config file instead of busybox.config and will be booting in a few
>> >> minutes to see how that goes...
>> >
>> >Not sure if I am following you. I think you may be getting the kernel 
>> >config and the busybox config confused. The documentation for customizing 
>> >busybox does not mention modifying the kernel, but what I did to customize 
>> >the kernel is something like the following.
>> >
>> >cd build_i386/linux-2.6.19.1
>> >cp .config .config.original
>> >make mrproper
>> >make menuconfig
>> >(set the kernel options you require)
>> >cd ../../
>> >make
>> 
>> there is a make linux26-menuconfig target for that (for i386 with
>> the generic x86 target support option turned on, at least).
>> 
>
>ok, i determined that the missing piece is that the ramdisk block device 
>needs to be set to compile in, not be a module.  to make an iso function, 
>i also had to hack in a makefile entry for LINUX_KERNEL (i just set it to 
>LINUX26_KERNEL).  after that things started working.  i also seem to see 
>an ordering problem that if i made a kernel change, i had to run make 
>twice in order for that to get into the iso.

That's inconvenient, yes. The problem i faced (wrt the ordering) is that
it's currently not possible to e.g. maintain a list of
LINUX26_KERNEL_PATCHES that would be populated by package/* and that
would be applied to the kernel(-headers) sources used for toolchain/*.

It resembles a little bit of a chicken and egg problem: Certain stuff
(from the toolchain) have to be known for correct package configuration
while the package-config _may_ impose changes to the toolchain.

I didn't pursue this issue (yet), perhaps somebody else is interrested
in looking at it?
>
>i'm not sure where those two changes should be done officially, or i'd 
>submit a patch.  it seems that if the iso relies on ramdisk support, then 
>it makes sense to have that enabled by default, and the LINUX_KERNEL vs 
>LINUX26_KERNEL make var should be addressed.  

Care to send your patch to outline what could be done to resolve this?
TIA,

[Buildroot] Kernel Panic .....

[Joe Pruett]

> >i'm not sure where those two changes should be done officially, or i'd 
> >submit a patch.  it seems that if the iso relies on ramdisk support, then 
> >it makes sense to have that enabled by default, and the LINUX_KERNEL vs 
> >LINUX26_KERNEL make var should be addressed.  
> 
> Care to send your patch to outline what could be done to resolve this?

the kernel change was done by running make linux26-menuconfig and changing 
the ramdisk device from m to y.  so that maybe goes into 
target/device/x86/i386/linux26.config

and the change i made for LINUX_KERNEL was to add the line:
LINUX_KERNEL=$(LINUX26_KERNEL)

into target/device/x86/i386/linux26.mk

but i'm not sure those are the right places to do things.  maybe the uses 
of LINUX_KERNEL should be changed to LINUX26_KERNEL?  and i'm not sure the 
linux26.config is really used to config things.