lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2AC135F730C4A045BAE4F1C1CB83FD4B03EF6F89@exch03.qd.lucent.com>
Date:	Sat, 28 Apr 2007 22:15:28 +0800
From:	"Shan, Guo Wen (Gavin)" <gshan@...atel-lucent.com>
To:	"Shan, Guo Wen (Gavin)" <gshan@...lucent.com>,
	<linux-kernel@...r.kernel.org>
Subject: RE: The kernel keeps spwaning /bin/sh at booting time


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@...r.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ