From: Tore Martin Hagen <thagen@slb•com>
To: linuxppc-embedded@ozlabs•org
Subject: Re: All children killed in /sbin/init
Date: Tue, 28 Feb 2006 09:36:32 +0100 [thread overview]
Message-ID: <44040B90.3050708@slb.com> (raw)
In-Reply-To: <43F03632.9060609@slb.com>
For Archive reasons I am posting the solution to my problem.
The problem was a missing patch to the arch/ppc/kernel/cputable.c (got
it from Montavista)
--- arch/ppc/kernel/cputable.c.orig Tue Jul 6 11:22:03 2004
+++ arch/ppc/kernel/cputable.c Tue Jul 6 11:25:49 2004
@@ -289,6 +289,14 @@
32, 32,
__setup_cpu_603
},
+ { /* 8280 is a G2_LE (603e core, plus some) */
+ 0x7fff0000, 0x00820000, "8280",
+ CPU_FTR_SPLIT_ID_CACHE | CPU_FTR_CAN_DOZE | CPU_FTR_USE_TB |
+ CPU_FTR_CAN_NAP | CPU_FTR_HAS_HIGH_BATS,
+ COMMON_PPC,
+ 32, 32,
+ __setup_cpu_603
+ },
{ /* default match, we assume split I/D cache & TB (non-601)... */
0x00000000, 0x00000000, "(generic PPC)",
CPU_FTR_SPLIT_ID_CACHE | CPU_FTR_USE_TB | CPU_FTR_HPTE_TABLE,
/Tore
Tore Martin Hagen wrote:
>Hi,
>
>I have a custom board with MPC8275 and NFS root file system. I use
>u-boot to load the kernel and it boots up, mounts the file system and
>starts /sbin/init. Then all the children of init dies, I get the
>following errors (with Debugging enabled in /sbin/init)
>
>Sending DHCP requests .,
>OK
>
>IP-Config: Got DHCP answer from 10.0.0.1, my address is
>10.0.0.111
>IP-Config:
>Complete:
>
> device=eth0, addr=10.0.0.111, mask=255.255.255.0,
>gw=10.0.0.1,
> host=10.0.0.111, domain=,
>nis-domain=(none),
> bootserver=10.0.0.1, rootserver=10.0.0.1,
>rootpath=/local/Mpc8266ads/Box2/root
>NET4: Unix domain sockets 1.0/SMP for Linux
>NET4.0.
>Looking up port of RPC 100003/2 on
>10.0.0.1
>Looking up port of RPC 100005/1 on
>10.0.0.1
>VFS: Mounted root (nfs
>filesystem).
>
>Mounted devfs on
>/dev
>
>Freeing unused kernel memory: 96k
>init
>
>INIT: version 2.78 booting
>INIT: Reading
>inittab
>
>INIT: Checking for children to
>kill
>INIT: Checking for children to
>start
>INIT: Started id si (pid
>11)
>
>INIT: init_main:
>waiting..
>
>INIT: chld_handler: marked 11 as
>zombie
>INIT: got
>SIGCHLD
>
>INIT: Child died, PID=
>11
>
>INIT: Checking for children to
>start
>INIT: SYSINIT ->
>BOOT
>
>INIT: init_main:
>waiting..
>
>INIT: Checking for children to
>start
>INIT: BOOT ->
>NORMAL
>
>INIT: Entering runlevel:
>3
>
>INIT: init_main:
>waiting..
>
>INIT: Checking for children to
>start
>INIT: Started id tmh (pid
>14)
>
>INIT: init_main:
>waiting..
>
>INIT: chld_handler: marked 14 as
>zombie
>INIT: got
>SIGCHLD
>
>INIT: Child died, PID= 14
>.....
>
>The file system works fine on my MPC8266ADS board.
>
>Do I have a problem with the mounting of the file system, or is there
>something wrong with my MMU?
>
>The kernel is compiled with CONFIG_PPC_STD_MMU=y
>
>Any suggestions about where i should start digging would be appreciated.
>
>/Tore Martin Hagen
>
>
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs•org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
prev parent reply other threads:[~2006-02-28 8:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 7:33 All children killed in /sbin/init Tore Martin Hagen
2006-02-28 8:35 ` Tore Martin Hagen
2006-02-28 8:36 ` Tore Martin Hagen [this message]
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=44040B90.3050708@slb.com \
--to=thagen@slb$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)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