All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Vinokurov <d.vinokuroff@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Serial console problem: Id "S0" respawning too fast
Date: Thu, 21 Jan 2010 12:57:34 +0500	[thread overview]
Message-ID: <4B5808EE.9010909@gmail.com> (raw)

Hello,

I want to set up board only with serial console interface (no tty0).

Kernel bootargs: console=ttyS0,115200n81 root=/dev/nfs rw 
nfsroot=192.168.0.100:/srv/nfs/armrfs ip=dhcp init=/sbin/init

Inittab has only one getty line: S0:2345:respawn:/sbin/getty 115200 ttyS0

I can see boot log, but it is really hard to login. And even if I could 
login, it's impossible to execute any commands, shell dies and login 
message appear again. Here is log of what usually happen:
------------------------------------------------
OpenEmbedded Linux phy3250 ttyS0

minimal .dev-snapshot-20100119 phy3250 ttyS0

phy3250 login: root
O
O
O
OpenEmbedded Linux phy3250 ttyS0

minimal .dev-snapshot-20100119 phy3250 ttyS0

phy3250 login: r
OpenEmbedded Linux phy3250 ttyS0

minimal .dev-snapshot-20100119 phy3250 ttyS0

phy3250 login: root
O
O
INIT: Id "S0" respawning too fast: dis
INIT: no more processes left in this r

O
O
O
O
O
O
O
O
O
INIT: Id "S0" respawning too fast: dis

O
O
O
O
O
O
O
O
O
INIT: Id "S0" respawning too fast: dis
------------------------------------------------

Tried to decrease baudrate to 38400 -- same trouble. Really don't know 
what to do with it. Maybe I miss some kernel or getty options or 
something else?

-- 
Best Regards,
Dmitry Vinokurov
<d.vinokuroff@gmail.com>




             reply	other threads:[~2010-01-21  7:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21  7:57 Dmitry Vinokurov [this message]
2010-01-21  9:26 ` Serial console problem: Id "S0" respawning too fast Dmitry Vinokurov

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=4B5808EE.9010909@gmail.com \
    --to=d.vinokuroff@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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.