hi Nate,
thanks for your reply,
and it's found the /init succesfully,
because there are some problem in mmcblk1p2..
but shows the other problem now,
when kernel executing /init,
the kernel will be stuck for 60 seconds and shows message:
BUG: soft lockup - CPU#0 stuck for 61s! [init:1]
however, I try to change boot args in my u-boot for init parameter,
from init=/init to init=/system/bin/sh
and the error message will be
Kernel panic - not syncing: Attempted to kill init!
these two problem have the same condition,
problem is in execute the *run_init_process* function,
for run_init_process("/init") the kernel shows soft lock,
and run_init_process("/system/bin/sh") appears kernel panic,
if you have any suggestion, please tell me,
thanks a lot!
stanly
2011/3/19 Nate H <[email protected]>
> What's your kernel command? I mean something like "noinitrd root=/dev/nfs
> init=/linuxrc"
>
>
> 2011/3/18 Amit Pundir <[email protected]>
>
>> Does your /init has executable permission?
>>
>> Regards,
>> Amit Pundir
>>
>> 2011/3/18 tstanly <[email protected]>:
>> > hi Jiejing,
>> >
>> > yes I really have, thanks
>> >
>> > On 3月17日, 下午11時42分, "Jiejing.Zhang " <[email protected]> wrote:
>> >> Hi，
>> >>
>> >> do you have /init in your mmcbk1p2 ?
>> >>
>> >> Best regards,
>> >> Zhang Jiejing
>> >>
>> >> 2011/3/17 tstanly <[email protected]>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> > 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 <[email protected]> wrote:
>> >> > > should you ramdisk issue. Please check your kernel option and
>> bootloader
>> >> > setting
>> >>
>> >> > > Jiejing
>> >>
>> >> > > 在 Mar 17, 2011，17:09，stanly <[email protected]> 写道：
>> >>
>> >> > > > 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: [email protected]
>> >> > > > website:http://groups.google.com/group/android-kernel
>> >>
>> >> > --
>> >> > unsubscribe: [email protected]
>> >> > website:http://groups.google.com/group/android-kernel
>> >
>> > --
>> > unsubscribe: [email protected]
>> > website: http://groups.google.com/group/android-kernel
>>
>> --
>> unsubscribe: [email protected]
>> website: http://groups.google.com/group/android-kernel
>
>
>
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-kernel
