All of lore.kernel.org
 help / color / mirror / Atom feed
From: srinidhi.m26@gmail.com (Srinidhi M)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Not getting login prompt after CPU entered into cpu_idle() state
Date: Fri, 6 Jul 2012 14:09:29 +0530	[thread overview]
Message-ID: <CADa7JjW-WEy9tQBd-MCitH3eqan8UmYRzOMxGUCsePwVJG=quA@mail.gmail.com> (raw)
In-Reply-To: <CAE6JOJ_=Wf_g03vQKfuFEMijib+0Eg6mwftmiDvoTgMsLAsm2A@mail.gmail.com>

On Fri, Jul 6, 2012 at 1:10 AM, sk.syed2 <sk.syed2@gmail.com> wrote:
>> Here are the final debug statements which we are seeing in the hyper terminal.
>
> Can you post the full logs WITHOUT your debug prints. What is the
> toolchain you are using?

Please find the attached FULL log file without our own messages.

>> If we load 2.6.10 kernel image, we are getting login prompt in the
>> hyper terminal on the same Phytec board.
>
> You can isolate the problem by writing a small utility(blinky) which
> would blink some LED on the board and then pass (init = /sbin/blinky)
> it in your kernel command line.

We are assuming that the kernel is completely booted, in 2.6.32
kernel, without any issues as it entered into cpu_idle state. We are
guessing that there is an error in the file system sources (i.e.
sbin/init). Unfortunately, we do not have the sources for the
available file system and we have downloaded the file system from the
following Phytec link.

http://www.phytec.com/products/linux/bsp-LPC3180.html

Please provide some insight to find out the reason for not getting login prompt.

Thanks and Regards,
Srinidhi M.

> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: logs_w_o_prints.txt
Url: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120706/5202187d/attachment-0001.txt 

  reply	other threads:[~2012-07-06  8:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-05  5:12 Not getting login prompt after CPU entered into cpu_idle() state Srinidhi M
2012-07-05 17:56 ` Mulyadi Santosa
2012-07-05 18:02   ` Jonathan Neuschäfer
2012-07-05 19:25     ` Mulyadi Santosa
2012-07-05 19:40 ` sk.syed2
2012-07-06  8:39   ` Srinidhi M [this message]
2012-07-06 21:40     ` Philipp Ittershagen
2012-07-06 23:23     ` sk.syed2
2012-07-09 13:36       ` Srinidhi M
2012-07-09 13:47         ` Philipp Ittershagen
  -- strict thread matches above, loose matches on Subject: below --
2012-07-04 12:51 Srinidhi M

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADa7JjW-WEy9tQBd-MCitH3eqan8UmYRzOMxGUCsePwVJG=quA@mail.gmail.com' \
    --to=srinidhi.m26@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.