From: "Ing.Gianfranco Morandi" <gianfranco.morandi@euro-studio•it>
To: "LinuxPPC" <linuxppc-embedded@lists•linuxppc.org>
Subject: respawning too fast
Date: Fri, 25 Oct 2002 11:28:16 +0200 [thread overview]
Message-ID: <007c01c27c08$d9bb2b60$0700a8c0@pc005> (raw)
Finally I have solved the starting problem on my EST8260 board. I have
burned the flash with the PPCboot 1.20 and I've been able to load any
kernel: M.V. 2.4.2 and ELDK 2.4.4.
Now I was trying to go ahead with a newer version of kernel (i.e. 2.4.18)
and now this is what happens:
BOOTP broadcast 1
ARP broadcast 1
TFTP from server 10.0.0.10; our IP address is 10.0.0.20
Filename '/tftpboot/image'.
Load address: 0x500000
Loading: #################################################################
###############################
done
Bytes transferred = 491392 (77f80 hex)
## Booting image at 00500000 ...
Image Name: FEC-Linux 2.4.18
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 491328 Bytes = 479.8 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Memory BAT mapping: BAT2=64Mb, BAT3=0Mb, residual: 0Mb
..................
..................
Sending BOOTP requests . OK
IP-Config: Got BOOTP answer from 10.0.0.10, my address is 10.0.0.20
IP-Config: Complete:
device=eth0, addr=10.0.0.20, mask=255.0.0.0, gw=255.255.255.255,
host=10.0.0.20, domain=, nis-domain=(none),
bootserver=10.0.0.10, rootserver=10.0.0.10, rootpath=/opt/eldk/ppc_82xx
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 10.0.0.10
Looking up port of RPC 100005/1 on 10.0.0.10
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 52k init
tty_io.c: process 1 (swapper) used obsolete /dev/cua - update software to
use /d
ev/ttyS0
tty_io.c: process 1 (init) used obsolete /dev/cua - update software to use
/dev/
ttyS0
tty_io.c: process 1 (init) used obsolete /dev/cua - update software to use
/dev/
ttyS0
INIT: tty_io.c: process 1 (init) used obsolete /dev/cua - update software to
use
/dev/ttyS0
version 2.78 bootingtty_io.c: process 1 (init) used obsolete /dev/cua -
update s
oftware to use /dev/ttyS0
Welcome to DENX Embedded Linux Environment
Press 'I' to enter interactive startup.
Mounting proc filesystem: [ OK ]
Configuring kernel parameters: [ OK ]
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access
method.
Setting clock : Wed Dec 31 19:00:07 EST 1969 [ OK ]
Activating swap partitions: [ OK ]
Setting hostname 10.0.0.20: [ OK ]
Checking filesystems
Checking all file systems.
[ OK ]
Mounting local filesystems: [ OK ]
Enabling swap space: [ OK ]
INIT: Entering runlevel: 3
Entering non-interactive startup
Starting system logger: [ OK ]
Starting kernel logger: [ OK ]
Starting xinetd: [ OK ]
INIT: Id "3" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel
I don't understand the messages related to the /dev/cua (these messages were
not present with the ELDK) and why the INIT process doesn't let me get the
console prompt.
Any suggestions?
Thanks
Gianfranco
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-10-25 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 9:28 Ing.Gianfranco Morandi [this message]
2002-10-26 7:44 ` respawning too fast fred
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='007c01c27c08$d9bb2b60$0700a8c0@pc005' \
--to=gianfranco.morandi@euro-studio$(echo .)it \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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