Kernel panic - not syncing: Attempted to kill init!

Neeraj Vaidya neeraj.vaidya at
Fri Apr 17 01:49:41 PDT 2009

One reason could be that you need a large initial ramdisk (initrd). You can customize it using the GRUB command line parameter as follows :
ramdisk_size = 90000k
This is for a 90MB ramdisk.
Note that this size is to be specified in KB and hence the 'k' appended to the number of KBs

Another possible reason for the kernel panic error could be that you have created the ramdisk using EXT3 fs and your kernel cannot mount this ramdisk if it does not have ext3.ko module built-in the kernel image.

Cheers !


----- Original Message ----
From: Mike McCarty <Mike.McCarty at>
To: LFS Support List <lfs-support at>
Sent: Thursday, 16 April, 2009 11:56:22 AM
Subject: Re: Kernel panic - not syncing: Attempted to kill init!

ForrestG wrote:
> I have 256MB ram but motherboard detect only 128MB

Well, that looks like a problem, but it doesn't
look like the cause of your boot failure.

The error report looks like you are using too much stack. If
so, then the problem is not insufficient RAM. Unless you
use a RAM disc, and that's eaten everything. Do you
have a RAM disc, and if so how big is it?

Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
Unsubscribe: See the above information page

      Add more friends to your messenger and enjoy! Go to

More information about the lfs-support mailing list