From: "Shan, Guo Wen (Gavin)" <gshan@alcatel-lucent.com>
To: "Shan, Guo Wen (Gavin)" <gshan@qd.lucent.com>,
<linux-kernel@vger.kernel.org>
Subject: RE: The kernel keeps spwaning /bin/sh at booting time
Date: Sat, 28 Apr 2007 22:15:28 +0800 [thread overview]
Message-ID: <2AC135F730C4A045BAE4F1C1CB83FD4B03EF6F89@exch03.qd.lucent.com> (raw)
Pls ignore this question. The error cause by the fifosize of port. I haven't set the fifo size for port, which caused this problem.
-----Original Message-----
From: Shan, Guo Wen (Gavin)
Sent: Saturday, April 28, 2007 9:18 PM
To: linux-kernel@vger.kernel.org
Subject: The kernel keeps spwaning /bin/sh at booting time
Hi,
The system keeps spwaning /bin/sh at booting time. I'm using busybox1.5. Do you have any ideas?
v_console_console_init: try to register CONSOLE driver
register_console: name ttyVC, index 1, a0=0xc02e910c, a1=0xc000380c,a2=0xc0006378
register_console: console ttyVC, cmd line ttyMM
register_console: console ttyVC1 IS the one !!!!!!
**************************************************************
name: ttyVC, index: 1, flags: 0x00000017
name: ttyMM, index: 0, flags: 0x00000005
**************************************************************
v_console_console_init: register CONSOLE driver sucessfully
Freeing unused kernel memory: 1536k init
Warning: unable to open an initial console.
Please press Enter to activate this console. init: can't log to /dev/tty5
starting pid 191, tty '/dev/ttyS1': '/bin/sh'
#
Please press Enter to activate this console. init: can't log to /dev/tty5
starting pid 192, tty '/dev/ttyS1': '/bin/sh'
#
Please press Enter to activate this console. init: can't log to /dev/tty5
starting pid 193, tty '/dev/ttyS1': '/bin/sh'
#
Please press Enter to activate this console. init: can't log to /dev/tty5
starting pid 194, tty '/dev/ttyS1': '/bin/sh'
#
Please press Enter to activate this console. init: can't log to /dev/tty5
starting pid 195, tty '/dev/ttyS1': '/bin/sh'
#
Please press Enter to activate this console. init: can't log to /dev/tty5
starting pid 196, tty '/dev/ttyS1': '/bin/sh'
#
Please press Enter to activate this console. init: can't log to /dev/tty5
starting pid 197, tty '/dev/ttyS1': '/bin/sh'
#
Please press Enter to activate this console. init: can't log to /dev/tty5
starting pid 198, tty '/dev/ttyS1': '/bin/sh'
#
Please press Enter to activate this console. init: can't log to /dev/tty5
starting pid 199, tty '/dev/ttyS1': '/bin/sh'
Thanks,
Gavin
next reply other threads:[~2007-04-28 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 14:15 Shan, Guo Wen (Gavin) [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-28 13:17 Shan, Guo Wen (Gavin)
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=2AC135F730C4A045BAE4F1C1CB83FD4B03EF6F89@exch03.qd.lucent.com \
--to=gshan@alcatel-lucent.com \
--cc=gshan@qd.lucent.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®