All children killed in /sbin/init
For Archive reasons I am postin the sollution 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) */
+ 0x7fff, 0x0082, 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)... */
0x, 0x, (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 13/2 on
10.0.0.1
Looking up port of RPC 15/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
All children killed in /sbin/init
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) */
+ 0x7fff, 0x0082, 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)... */
0x, 0x, (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 13/2 on
10.0.0.1
Looking up port of RPC 15/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
All children killed in /sbin/init
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 13/2 on 10.0.0.1 Looking up port of RPC 15/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
HELP! Memory mapping and address space doubts
Hi Vitaly,
It seams that you are mixing virtual addresses and physical addresses.
You must put RAM at physical address 0 and you can keep the flash and
fpga as it is. The 0xc000 is the virtual address of the kernel, and
has nothing to do with the physical address.
Where have you mapped the IMMR?
If you have problems with probing of the CFI flash I would try to find
out what the problem realy is. I was given a board with what I would
call SwapEndian, I had to use littleendian for read and bigendian for
writes.
/Tore Martin Hagen
Jose Fran?a (Ext_GTBC) wrote:
Vitaly,
I'm using a linux 2.4.31 kernel. In the present situation I have BRx/ORx
well configured and i can boot u-boot normally and without problems. I have a
flash eprom with base address 0xD000 and a FPGA in 0xE000. In linux,
i have the mtd driver similar to the rpxlite board. cfi_probe doesn't find my
flash eprom. My colleague developped an fpga driver, but he can't access it
either... It seem's that all the addresses that we try to access are all
mixed-up. In ppc_md.map_io, i'm doing io_block_mapping for the CPM (from
0xf000 to the end of memory) , 0x8000 and 0xa000 for PCI address
space, both with 256MB of length. We are a bit lost... It seems that we
forgot something to do. Can you help me on this?
Best regards,
Filipe.
-Mensagem original-
De: linuxppc-embedded-bounces at ozlabs.org em nome de Vitaly Bordug
Enviada: sex 27-01-2006 13:37
Para: Jose Fran?a (Ext_GTBC)
Cc: linuxppc-embedded at ozlabs.org
Assunto: Re: HELP! Memory mapping and address space doubts
Jose,
Can you please be a bit more specific in targets you want to achieve?
An example how to setup br/or and use the device could be found as a
part of PQ2 PCI support,
where interrupt controller is implemented as a CPLD device
(arch/ppc/syslib/m82xx_pci.{c,h}).
On Thu, 26 Jan 2006 14:04:49 -
Jose Fran?a (Ext_GTBC) Jose.Franca.Ext at siemens.com wrote:
Hello u all!
I need to clarify some aspects of the memory management in ppc
linux and i hope that you could help me.
Lets imagine we have a mpc8272 based board with 3 devices A, B
and C.In the bootloader (in my case, i use u-boot), i configured the BRx and
Orx so that A has base address X, B has base address Y and C has base address
Z. My first doubt arrises here: what address should i use? Being SDRAM base
address 0x and kernel base address 0xC000, where will i put these
devices mapped on? Above 0xC000 or in between the end of physical memory
and 0xC000? Do i really need to configure the BAT registers in u boot?
In linux 2.4 kernel, we have ppc_md.setup_io_mappings to map
address blocks into the BAT registers... As i observed in the kernel source
tree examples, we must map CPM (why?). And what about the other devices A, B
and C? How will i setup them in this case and what addresses i can use? Above
0xC000 or in between the end of physical memory and 0xC000? Is the
SDRAM included?
Thanks in advance to all contributions! All of them will be
most welcomed!
Best regards,
Filipe
___
Linuxppc-embedded mailing list
Linuxppc-embedded at ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
--
Sincerely,
Vitaly
___
Linuxppc-embedded mailing list
Linuxppc-embedded at ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
___
Linuxppc-embedded mailing list
Linuxppc-embedded at ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
NFS can not mount (linuxppc2.2.4 mpc5200 lxt971)
wrote: eth0: config: auto-negotiation on, 100HDX, 10HDX. IP-Config: Complete: device=eth0, addr=198.87.102.211, mask=255.255.255.0, gw=198.87.102.140, host=oops, domain=, nis-domain=(none), bootserver=198.87.102.140, rootserver=198.98.102.140, rootpath= Hi Check out your DHCP server. You don't get the rootpath from it. /etc/dhcpd.conf should contain option root-path /local/Mpc8266ads/Box0/root; or something similar. also take a look in /var/log/messages to pinpoint the problem. /Tore Hagen
Help on 8260 board
Hi, To change u-boot for your needs you will need to do approximately the following: copy include/configs/MPC8260ADS.h to include/configs/YOURBOARD8260.h Print out the the file and sit down with the 8260 ref. manual. Adjust the YOURBOARD8260.h to fit your needs. (If you are not a HW designer this will definitely take you some time) Added a new directory board/yourboard8260 copied the following files from board/mpc8266ads to board/fox8275: config.mk flash.c Makefile mpc8260ads.c - yourboard8260.c u-boot.lds Changed the files to fit the your board. Changed the main Makefile to support a new target YOURBOARD8260_config:unconfig @./mkconfig $(@:_config=) ppc mpc8260 yourboard8260 good luck
RMII support for MPC8280
Hi. Has anybody made u-boot (1.1.2) with support for RMII on the MPC8280? The code currently only supports the MII interface. /Tore
Problem related to root filesystem
Hi Apoorv. Is the Flash CFI complient? The sharp flash that commes with the ADS8260 board is not. /Tore apoorv sangal wrote: Hi All, I am porting Linux on the custom board PMC8266 (having MPC8266 microprocessor) based on the ADS8260 board.I am using ELDK1.1.1 and Linux2.4.24. I am trying to load JFFS2 filesystem , the JFFS2 filesystem image is at address 0xFC16 and the flash size is 32mb I am getting the following messages:- physmap flash device: 200 at fc16 CFI: Found no Physically mapped flash device at location zero kmod: failed to exec /sbin/modprobe -s -k jedec_probe, errno = 2 kmod: failed to exec /sbin/modprobe -s -k map_rom, errno = 2 pmc8260 flash map (size-0x200 mem-0xFC16) CFI: Found no pmc8260 flash memory device at location zero Can anyone please tell me what is happening and how can i set it right?? * The whole of captured output is as following:- * Image Name: 2.4.24 ADS8260 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:302270 Bytes = 295.2 kB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... Linux version 2.4.24-pre2 (satyam at pmcserver) (gcc version 3.2.2 20030217 (Yellow Dog Linux 3.0 3.2.2-2a_1)) #20 Fri Aug 5 15:22:28 IST 2005 On node 0 totalpages: 32768 zone(0): 32768 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: console=ttyS0,115200 root=FC16 rw rootfstype=jffs2 Warning: real time clock seems stuck! Calibrating delay loop... 131.89 BogoMIPS Memory: 128712k available (512k kernel code, 260k data, 36k init, 0k highmem) Dentry cache hash table entries: 16384 (order: 5, 131072 bytes) Inode cache hash table entries: 8192 (order: 4, 65536 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 8192 (order: 3, 32768 bytes) Page-cache hash table entries: 32768 (order: 5, 131072 bytes) POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Starting kswapd Inside Chr_dev_init CPM UART driver version 0.01 ttyS0 on SMC1 at 0x, BRG7 ttyS1 on SMC2 at 0x0040, BRG8 ttyS2 on SCC1 at 0x8000, BRG1 ttyS3 on SCC2 at 0x8100, BRG2 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize physmap flash device: 200 at fc16 CFI: Found no Physically mapped flash device at location zero kmod: failed to exec /sbin/modprobe -s -k jedec_probe, errno = 2 kmod: failed to exec /sbin/modprobe -s -k map_rom, errno = 2 pmc8260 flash map (size-0x200 mem-0xFC16) CFI: Found no pmc8260 flash memory device at location zero * VFS:test name = /dev/root VFS:fs_name = jffs2 VFS:root name = 00:00 kmod: failed to exec /sbin/modprobe -s -k jffs2, errno = 2 VFS:tried fs_name = jffs2 err = -19 VFS: Cannot open root device FC16 or 00:00 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 00:00 0Rebooting in 180 seconds.. Response awaited from the list. Regards, Apoorv Sangal ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Reseting bootcount from linux
Hi, I am using a MPC8266ADS-PCI board and u-boot with the CONFIG_BOOTCOUNT_LIMIT. If i stop u-boot before it starts Linux I can see that the bootcount variable increments nicely. But if i dump the content from flash (dd if=/dev/mtd/1 of=a1out bs=1k) and check the content it is always bootcount=1 So how can I reset the bootcount if it is always 1, or rather where is the real bootcount stored? /Tore **
