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

[Philipp Ittershagen <p.ittershagen@xxxxxxxxxxxxxx>]

On Mon, Jul 9, 2012 at 3:36 PM, Srinidhi M <srinidhi.m26@xxxxxxxxx> wrote:
> So, we have built busybox with the same tool chain version that we
> used to build the 2.6.32 kernel image. Even though, we are seeing the
> same error messages i.e. we are seeing 5 to 6 "/sbin/modprobe" calls
> after calling the "/sbin/init". After that, we did not see any
> messages at all. We are getting the SAME log messages that we got
> earlier when we use this busybox file system which was build with same
> tool chain.

My next guess would be that some tty device nodes changed and your
init configuration at /etc/inittab points to wrong console devices. At
least that was the case when I had a similar error. Init starts and
puts the login prompt on the wrong console device so you don't see it.


Greetings,

  Philipp

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies