hi,

I think my bootloader args is correct,
bootargs=console=ttyO2,115200n8 rootdelay=1 init=/init root=/dev/
mmcblk1p2 ...........

but I can't understand it's a ramdisk issue?
can you give me some hint?
thanks

On 3月17日, 下午5時14分, gmail <kzj...@gmail.com> wrote:
> should you ramdisk issue.  Please check your kernel option and bootloader 
> setting
>
> Jiejing
>
> 在 Mar 17, 2011,17:09,stanly <tsai.sta...@gmail.com> 写道:
>
>
>
>
>
>
>
> > hi all,
>
> > I have developed in kernel 2.6.35
> > and when booting up kernel,
> > there have some problems bellow,
> > I get the "failed to execute /init" message,
> > but there really exist init
> > can somebody give me suggestion?
> > thanks so much
> > ===============================
> > EXT3-fs: barriers not enabled
> > kjournald starting.  Commit interval 5 seconds
> > EXT3-fs (mmcblk0p2): using internal journal
> > EXT3-fs (mmcblk0p2): recovery complete
> > EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
> > VFS: Mounted root (ext3 filesystem) on device 179:2.
> > Freeing init memory: 208K
> > Failed to execute /init.  Attempting defaults...
> > Kernel panic - not syncing: No init found.  Try passing init= option to 
> > kernel. See Linux Documentation/init.txt for guidance.
> > [<c0041b8c>] (unwind_backtrace+0x0/0xe4) from [<c0487aac>] (panic+0x54/0xdc)
> > [<c0487aac>] (panic+0x54/0xdc) from [<c003c5c4>] (init_post+0xac/0xd4)
> > [<c003c5c4>] (init_post+0xac/0xd4) from [<c00084e4>] 
> > (kernel_init+0x174/0x1f0)
> > [<c00084e4>] (kernel_init+0x174/0x1f0) from [<c003d97c>] 
> > (kernel_thread_exit+0x0/0x8)
> > Rebooting in 1 seconds..
> > ===============================
> > --
> > unsubscribe: android-kernel+unsubscr...@googlegroups.com
> > website:http://groups.google.com/group/android-kernel

-- 
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel

Reply via email to