Yeap, take the one that does boot out of the loop. Then try booting the other two. If the first to boot works. Then you have a problem with your configuration, or possibly network.
Are you using GbE + GbE switch between the server, and the bones ? On Wed, Jul 8, 2015 at 12:18 PM, <g...@novadsp.com> wrote: > 3 B3s all same rev all running 4.1.0-bone9 configured identically to boot > via TFTP/NFS (not all at the same time I hasten to add). 1 machine works > perfectly. The other 2 both reach the same point then hang. Any thoughts? > > > > TAIA > > > > [ 0.000000] Booting Linux on physical CPU 0x0 > > [ 0.000000] Initializing cgroup subsys cpuset > > [ 0.000000] Initializing cgroup subsys cpu > > [ 0.000000] Initializing cgroup subsys cpuacct > > [ 0.000000] Linux version 4.1.0-bone9 (jevans@acermint) (gcc version > 4.9.3 20141031 (prerelease) (Linaro GCC 2014.11) ) #1 Wed Jul 1 13:31:10 > BST 2015 > > [ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), > cr=50c5387d > > [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing > instruction cache > > [ 0.000000] Machine model: TI AM335x BeagleBone Black > > [ 0.000000] cma: Reserved 16 MiB at 0x9f000000 > > [ 0.000000] Memory policy: Data cache writeback > > [ 0.000000] CPU: All CPU(s) started in SVC mode. > > [ 0.000000] AM335X ES2.0 (sgx neon ) > > [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. > Total pages: 129920 > > [ 0.000000] Kernel command line: console=ttyO0,115200n8 root=/dev/nfs > rw rootfstype=ext4 rootwait fixrtc > nfsroot=192.168.1.110:/home/bone/rootfs,vers=3 > ip=192.168.1.11:192.168.1.110:192.168.1.254:255.255.255.0::eth0:off > > xxx--------elided-------------xxx > > [ OK ] Started Trigger Flushing of Journal to Persistent Storage. > > [ OK ] Started LSB: Tune IDE hard disks. > > [ OK ] Started Create Volatile Files and Directories. > > Starting Network Time Synchronization... > > Starting Update UTMP about System Boot/Shutdown... > > [ OK ] Started Update UTMP about System Boot/Shutdown. > > [ OK ] Started Network Time Synchronization. > > [ OK ] Reached target System Time Synchronized. > > [ OK ] Found device /dev/ttyO0. > > [ 12.709682] omap_rng 48310000.rng: OMAP Random Number Generator ver. 20 > > [ 12.966802] tda998x 0-0070: found TDA19988 > > [ 12.997206] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > > [ 13.004323] [drm] No driver support for vblank timestamp query. > > [ 13.070366] tilcdc 4830e000.lcdc: No connectors reported connected with > modes > > [ 13.134136] [drm] Cannot find any crtc or sizes - going 1024x768 > > [ 13.214789] Console: switching to colour frame buffer device 128x48 > > [ 13.227549] tilcdc 4830e000.lcdc: fb0: frame buffer device > > [ 13.233424] tilcdc 4830e000.lcdc: registered panic notifier > > [ 13.339779] [drm] Initialized tilcdc 1.0.0 20121205 on minor 0 > > [ 13.376166] omap-sham 53100000.sham: hw accel on OMAP rev 4.3 > > [ 13.432581] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2 > > [ ***] A start job is running for LSB: Raise network interf...28s / no > limit)[ 44.972386] nfs: server 192.168.1.110 not responding, still trying > > > > > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
