Not getting login prompt after CPU entered into cpu_idle() state

[Srinidhi M]

Hi All,

We have ported the kernel from 2.6.10 version to 2.6.32 kernel version
for our Phytec LPC-3180 board. We have done good work and able to
complete the kernel part i.e. completed the start_kernel function and
CPU entered into IDLE state from cpu_idle() function which is defined
in rest_init() function in main.c file. However, rest_init() function
also creates TWO threads. One thread is for running the kernel_init()
function where it calls the init_post() function. In this, after a few
other calls, there is a call to init the init-process i.e.
run_init_process("/sbin/init"). After this, we are not seeing neither
any errors nor login prompt in hyper terminal. We end up without
getting any login prompt. Any idea would be greatly help us in getting
the login prompt / for debugging the sources further for identifying
the exact reason / location to find out the error.

Here are the final debug statements which we are seeing in the hyper terminal.

<6>VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 1
<5>RAMDISK: gzip image found at block 0
VFS: Mounted root (ext2 filesystem) on device 1:0.
<6>Freeing init memory: 80K
.....@ <init/main.c>  <init_post>  <900>
.....@ <arch/arm/kernel/sys_arm.c>  <kernel_execve>  <271> ret = 0 : /sbin/init
.....@ <arch/arm/kernel/sys_arm.c>  <kernel_execve>  <274>
.....@ <arch/arm/kernel/sys_arm.c>  <kernel_execve>  <271> ret = 0 :
/sbin/modprobe
.....@ <arch/arm/kernel/sys_arm.c>  <kernel_execve>  <274>
.....@ <arch/arm/kernel/sys_arm.c>  <kernel_execve>  <271> ret = 0 :
/sbin/modprobe
.....@ <arch/arm/kernel/sys_arm.c>  <kernel_execve>  <274>
.....@ <arch/arm/kernel/sys_arm.c>  <kernel_execve>  <271> ret = 0 :
/sbin/modprobe
.....@ <arch/arm/kernel/sys_arm.c>  <kernel_execve>  <274>
.....@ <arch/arm/kernel/sys_arm.c>  <kernel_execve>  <271> ret = 0 :
/sbin/modprobe
.....@ <arch/arm/kernel/sys_arm.c>  <kernel_execve>  <274>

If we load 2.6.10 kernel image, we are getting login prompt in the
hyper terminal on the same Phytec board.

NOTE: We are using the same file system on 2.6.32 kernel which was
running fine on 2.6.10 kernel.

We will provide if any one need additional information / complete log.

Thanks in advance.

Regards,
Srinidhi.