Re: Kernel Panic - not syncing: Attempted to kill init! exitcode=0x0000000b

The first process that the *nix starts after booting up is init. The init process which has pid 1 live for as long as the host do not reboot. That message means that something has made init exit prematurely. Check your init.d, systemd or whatever init system you're using... Regards, 2016-08-22

Re: Kernel Panic - not syncing: Attempted to kill init! exitcode=0x0000000b

On Wed, Aug 17, 2016 at 7:05 AM, shobhit bhadani wrote: > >>Which version of kernel are you using? > > I am using kernel 3.8 Are you from the past? 3.8 was released more than 3 years ago!, Around the same day the metor exploted over Russia and the Pope resigned

Re: Kernel Panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Hi On Tuesday, August 16, 2016, shobhit bhadani wrote: > Hi, > > I am new to kernel. > What does this issue mean "not syncing: Attempted to kill init! "? > > Is this a user space issue? > > 17:10:09.0464-04:00 - Kernel panic - not syncing: Attempted to kill init!

Re: Kernel panic - not syncing: Attempted to kill init!

2011/7/13 史星星(研六 福州) shixingx...@ruijie.com.cn: Hi, I got a problem when trying to boot linux 2.6.32.13 on my Octeon CN5650 board. Booting logs below: ...omit…. EXT3-fs warning: maximal mount count reached, running e2fsck is recommended kjournald starting.  Commit interval 5

RE: Kernel panic - not syncing: Attempted to kill init!

boot option: root=/dev/mtdblock1 rootfstype=ext3 rw console=ttyS0,115200 mtdparts=phys_mapped_flash:1024k(bootloader)ro,256k(product_info),256k(system_para),128k(exception_info),128k(bootloader_env),-(reserve);gen_nand.0:128M(root),-(usr) boot logs: Using octmgmt0 device TFTP from server