Just a quick question, For Core 1 I am booting kernel using NFS. When I boot kernel on Core 1 it fails at following point. Attached are my DTS files for both cores. My NFS server is configured properly as I am booting Core 0 with the same server. I have used packet sniffer on my NFS server and I see no packet from Core 1 for my NFS server. Do you think this is problem in my DTS file or kernel configuration. Any help is appreciated.
........................ [ 88.940597] rxbd[5]: addr,vaddr=0xf777400,0xcf777400 [ 88.945561] rxbd[6]: addr,vaddr=0xf777800,0xcf777800 [ 88.950526] rxbd[7]: addr,vaddr=0xf777c00,0xcf777c00 OK [ 89.873634] ----PHY: skipping MII_CTRL1000 write. [ 89.957631] IP-Config: Guessing netmask 255.255.0.0 [ 89.962653] IP-Config: Complete: [ 89.965724] device=eth0, addr=<ip_address>, mask=255.255.0.0, gw=<gateway_ip>, [ 89.973843] host=<host_ip>, domain=, nis-domain=(none), [ 89.980025] bootserver=255.255.255.255, rootserver=<nfs_server_ip>, rootpath= [ 89.988012] Looking up port of RPC 100003/2 on 137.202.156.191 [ 90.877650] PHY: 0:01 - Link is Up - 1000/Full [ 124.993637] rpcbind: server <nfs_server_ip> not responding, timed out [ 125.000136] Root-NFS: Unable to get nfsd port number from server, using default [ 125.007458] Looking up port of RPC 100005/1 on <nfs_server_ip> [ 160.009636] rpcbind: server 137.202.156.191 not responding, timed out [ 160.016131] Root-NFS: Unable to get mountd port number from server, using default Regards, Farrukh Arshad -----Original Message----- From: Arshad, Farrukh Sent: Thursday, December 08, 2011 11:35 AM To: 'Scott Wood' Cc: Linuxppc-dev@lists.ozlabs.org Subject: RE: Multi-OS on P1022RDK Failing Thanks Scott. Fixing cpu 1 release address solved my problem. Also thanks for the CONFIG_LOWMEM_SIZE suggestions. Regards, Farrukh Arshad -----Original Message----- From: Scott Wood [mailto:scottw...@freescale.com] Sent: Thursday, December 08, 2011 2:24 AM To: Arshad, Farrukh Cc: Linuxppc-dev@lists.ozlabs.org Subject: Re: Multi-OS on P1022RDK Failing On 12/07/2011 08:57 AM, Arshad, Farrukh wrote: > Core 0 kernel > > CONFIG_LOWMEM_SIZE = 0x10000000 > > CONFIG_PHYSICAL_START = 0x00000000 > > > > Core 1 kernel > > CONFIG_LOWMEM_SIZE = 0x10000000 > > CONFIG_PHYSICAL_START = 0x10000000 Why are you messing with CONFIG_LOWMEM_SIZE? That adjusts the lowmem/highmem split, not the total amount of memory that this instance of Linux will use (though you may get that behavior as a side effect if highmem is disabled). U-boot should set the memory node in the device tree based on the bootm_low/bootm_size environment variables. > # Boot from NFS > > setenv core0nfsbootargs root=/dev/nfs nfsroot=$serverip:/$core0rootfs > ip=<dev_ip>::<nfs_server_ip>:::eth0:off rw debug > console=$consoledev0,$baudrate maxcpus=1 > > setenv core1nfsbootargs root=/dev/nfs nfsroot=$serverip:/$core1rootfs > ip=<dev_ip_2>::<nfs_server_ip>:::eth0:off rw debug > console=$consoledev0,$baudrate maxcpus=1 maxcpus should be unnecessary -- there will only be one cpu in the device tree for each partition. > My problem is Core 0 kernel is booting successfully but Core 1 kernel > hangs after uncompressing kernel image, and after that I don't see > anything on the console. > > > > Any thoughts on what I am missing or doing incorrect? The "cpu 1 release" command should be using the address of the decompressed kernel (should be $bootm_low), not where the uImage was loaded. Also, the two serial ports you're using share an interrupt -- this shouldn't stop kernel message output, but it's going to be a problem for userspace usage of the port. You should remove the interrupts property from the serial node in both partitions, so Linux will poll instead. -Scott
p1022rdk-core1.dts
Description: p1022rdk-core1.dts
p1022rdk-core0.dts
Description: p1022rdk-core0.dts
_______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
