This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

NFS Linux boot halts



Hello All,

I have a TMS8148 development board from Z3. I am trying to load the full EZSDK build onto it through NFS, however the boot process halts due to "not being able to connect to the NFS server" all of the sudden. It halts at the same place every time. I would be grateful for any advice. The boot log is attached. 

Regards,

Jakob

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2012.07.16 20:04:38 =~=~=~=~=~=~=~=~=~=~=~=
DRAM:  2 GiB
SW ECC selected
256 MiB
Using default environment

Net:   cpsw

NAND read: device 0 offset 0x80000, size 0x40000
 262144 bytes read: OK
## Starting application at 0x81000000 ...


U-Boot 2010.06 (Apr 24 2012 - 10:28:16)

TI8148-GP rev 2.1

ARM clk: 600MHz
DDR clk: 400MHz

I2C:   ready
DRAM:  2 GiB
NAND:  SW ECC selected
256 MiB
                          .:;rrr;;.                   
                    ,5#@@@@#####@@@@@@#2,             
                 ,A@@@hi;;;r5;;;;r;rrSG@@@A,          
               r@@#i;:;s222hG;rrsrrrrrr;ri#@@r        
             :@@hr:r;SG3ssrr2r;rrsrsrsrsrr;rh@@:      
            B@H;;rr;3Hs;rrr;sr;;rrsrsrsrsrsr;;H@B     
           @@s:rrs;5#;;rrrr;r#@H:;;rrsrsrsrsrr:s@@    
          @@;;srs&X#9;r;r;;,2@@@rrr:;;rrsrsrsrr;;@@   
         @@;;rrsrrs@MB#@@@@@###@@@@@@#rsrsrsrsrr;;@@  
        G@r;rrsrsr;#X;SX25Ss#@@#M@#9H9rrsrsrsrsrs;r@G 
        @9:srsrsrs;2@;:;;:.X@@@@@H::;rrsrsrsrsrsrr:3@ 
       X@;rrsrsrsrr;XAi;;:&@@#@Bs:rrsrsrsrsrsrsrsrr;@X
       @#;rsrsrsrsrr;r2ir@@@###::rrsrsrsrsrsrsrsrsr:@@
       @A:rrsrsrsrr;:2@29@@M@@@;:;rrrrsrsrsrsrsrsrs;H@
       @&;rsrsrsrr;A@@@@@@###@@@s::;:;;rrsrsrsrsrsr;G@
       @#:rrsrsrsr;G@5Hr25@@@#@@@#9XG9s:rrrrsrsrsrs:#@
       M@;rsrsrsrs;r@&#;::S@@@@@@@M@@@@Grr:;rsrsrsr;@#
       :@s;rsrsrsrr:M#Msrr;;&#@@@@@@@@@@H@@5;rsrsr;s@,
        @@:rrsrsrsr;S@rrrsr;:;r3MH@@#@M5,S@@irrsrr:@@ 
         @A:rrsrsrsrrrrrsrsrrr;::;@##@r:;rH@h;srr:H@  
         ;@9:rrsrsrsrrrsrsrsrsr;,S@Hi@i:;s;MX;rr:h@;  
          r@B:rrrrsrsrsrsrsrr;;sA@#i,i@h;r;S5;r:H@r   
           ,@@r;rrrsrsrsrsrr;2BM3r:;r:G@:rrr;;r@@,    
             B@Mr;rrrrsrsrsr@@S;;;rrr:5M;rr;rM@H      
              .@@@i;;rrrrsrs2i;rrrrr;r@M:;i@@@.       
                .A@@#5r;;;r;;;rrr;r:r#AsM@@H.         
                   ;&@@@@MhXS5i5SX9B@@@@G;            
                       :ihM#@@@@@##hs,                

Set defpowerlevel to 0x49
Net:   Detected MACID:40:5f:c2:25:c5:cb
cpsw
Hit any key to stop autoboot:  3  2  1  0 
Boot from TFTP and NFS...
Set powerlevel to 0x49
link up on port 0, speed 100, half duplex
Using cpsw device
TFTP from server 192.168.5.101; our IP address is 192.168.5.69
Filename '/images/uImage-dm814x-evm.bin'.
Load address: 0x81800000
Loading: *T #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 ###########################
done
Bytes transferred = 2796536 (2aabf8 hex)
## Booting kernel from Legacy Image at 81800000 ...
   Image Name:   Arago/2.6.37-psp04.04.00.01/dm81
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2796472 Bytes = 2.7 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (x0029463@swubn01) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Mon Apr 30 01:00:10 IST 2012

CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f

CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache

Machine: ti8148evm

vram size = 52428800 at 0x0

bootconsole [earlycon0] enabled

reserved size = 52428800 at 0x0

FB: Reserving 52428800 bytes SDRAM for VRAM

Memory policy: ECC disabled, Data cache writeback

OMAP chip is TI8148 2.0

SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000

Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 31904

Kernel command line: console=ttyO0,115200,quiet mem=176M vram=50M earlyprintk notifyk.vpssm3_sva=0xBF900000 noinitrd root=/dev/nfs nfsroot=192.168.5.29:/home/nemo-hd/targetfs,nolock,udp rw rootdelay=4 ip=192.168.5.69:192.168.5.101:192.168.5.253:255.255.255.0:Z3-DM814x::off

PID hash table entries: 512 (order: -1, 2048 bytes)

Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)

Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)

Memory: 126MB = 126MB total

Memory: 121500k/121500k available, 58724k reserved, 0K highmem

Virtual kernel memory layout:

    vector  : 0xffff0000 - 0xffff1000   (   4 kB)

    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)

    vmalloc : 0xcb800000 - 0xf8000000   ( 712 MB)

    lowmem  : 0xc0000000 - 0xcb000000   ( 176 MB)

    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)

    modules : 0xbf000000 - 0xbfe00000   (  14 MB)

      .init : 0xc0008000 - 0xc003d000   ( 212 kB)

      .text : 0xc003d000 - 0xc0549000   (5168 kB)

      .data : 0xc054a000 - 0xc0597200   ( 309 kB)

SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

NR_IRQS:407

IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts

Total of 128 interrupts on 1 active controller

GPMC revision 6.0

Trying to install interrupt handler for IRQ400

Trying to install interrupt handler for IRQ401

Trying to install interrupt handler for IRQ402

Trying to install interrupt handler for IRQ403

Trying to install interrupt handler for IRQ404

Trying to install interrupt handler for IRQ405

Trying to install interrupt handler for IRQ406

Trying to install type control for IRQ407

Trying to set irq flags for IRQ407

OMAP clockevent source: GPTIMER1 at 20000000 Hz

Console: colour dummy device 80x30

Calibrating delay loop... 599.65 BogoMIPS (lpj=2998272)

pid_max: default: 32768 minimum: 301

Security Framework initialized

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

devtmpfs: initialized

omap_voltage_early_init: voltage driver support not added

regulator: core version 0.5

regulator: dummy: 

NET: Registered protocol family 16

omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!

omap_voltage_add_dev: VDD specified does not exist!

OMAP GPIO hardware version 0.1

OMAP GPIO hardware version 0.1

OMAP GPIO hardware version 0.1

OMAP GPIO hardware version 0.1

omap_mux_init: Add partition: #1: core, flags: 4

NOR: Can't request GPMC CS

Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now

registered ti81xx_vpss device

registered ti81xx_vidout device

registered ti81xx on-chip HDMI device

registered ti81xx_fb device

registered ti81xx_vin device

ti81xx_pcie: Invoking PCI BIOS...

ti81xx_pcie: Setting up Host Controller...

ti81xx_pcie: Register base mapped @0xcb820000

ti81xx_pcie: Starting PCI scan...

PCI: bus0: Fast back to back transfers enabled

bio: create slab <bio-0> at 0

vgaarb: loaded

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

USBSS revision 4ea2080b

registerd cppi-dma Intr @ IRQ 17

Cppi41 Init Done

omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz

pcf857x: probe of 1-0021 failed with error -121

tps65910 1-002d: read from reg 3f failed

tps65910 1-002d: read from reg 1e failed

set_machine_constraints: failed to enable VRTC

tps65910 1-002d: failed to register tps65910-pmic regulator

tps65910-pmic: probe of tps65910-pmic failed with error -121

tps65910 1-002d: No interrupt support, no core IRQ

omap_i2c omap_i2c.3: bus 3 rev4.0 at 100 kHz

Advanced Linux Sound Architecture Driver Version 1.0.23.

Switching to clocksource gp timer

musb-hdrc: version 6.0, host, debug=0

musb-hdrc musb-hdrc.0: dma type: dma-cppi41

MUSB controller-0 revision 4ea20800

musb-hdrc musb-hdrc.0: MUSB HDRC host driver

musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1

usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

usb usb1: Product: MUSB HDRC host driver

usb usb1: Manufacturer: Linux 2.6.37 musb-hcd

usb usb1: SerialNumber: musb-hdrc.0

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

musb-hdrc musb-hdrc.0: USB Host mode controller at cb81e000 using DMA, IRQ 18

musb-hdrc musb-hdrc.1: dma type: dma-cppi41

MUSB controller-1 revision 4ea20800

musb-hdrc musb-hdrc.1: MUSB HDRC host driver

musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2

usb usb2: New USB device found, idVendor=1d6b, idProduct=0002

usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

usb usb2: Product: MUSB HDRC host driver

usb usb2: Manufacturer: Linux 2.6.37 musb-hcd

usb usb2: SerialNumber: musb-hdrc.1

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

musb-hdrc musb-hdrc.1: USB Host mode controller at cb826800 using DMA, IRQ 19

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 4096 (order: 3, 32768 bytes)

TCP bind hash table entries: 4096 (order: 2, 16384 bytes)

TCP: Hash tables configured (established 4096 bind 4096)

TCP reno registered

UDP hash table entries: 256 (order: 0, 4096 bytes)

UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

NET: Registered protocol family 1

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

RPC: Registered tcp NFSv4.1 backchannel transport module.

NetWinder Floating Point Emulator V0.97 (double precision)

PMU: registered new PMU device of type 0

omap-iommu omap-iommu.0: ducati registered

omap-iommu omap-iommu.1: sys registered

JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.

msgmni has been set to 237

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0

console [ttyO0] enabled, bootconsole disabled
console [ttyO0] enabled, bootconsole disabled

omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
brd: module loaded
loop: module loaded
ahci ahci.0: forcing PORTS_IMPL to 0x1
ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst 
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
omap2-nand driver initializing
NAND device: Manufacturer ID: 0xad, Chip ID: 0xda (Hynix )
Creating 6 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000020000 : "U-Boot-min"
0x000000020000-0x000000260000 : "U-Boot"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x0000006c0000 : "Kernel"
0x0000006c0000-0x00000cee0000 : "File System"
0x00000cee0000-0x000010000000 : "Reserved"
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffffc
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
CAN device driver interface
CAN bus driver for Bosch D_CAN controller 1.0
d_can d_can: d_can device registered (irq=52, irq_obj=53)
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
qt602240_ts 1-004a: __qt602240_read_reg: i2c transfer failed
qt602240_ts: probe of 1-004a failed with error -5
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
notify_init : notify drivercreated  for  remote proc id 2 at physical Address 0xbf900000
usbcore: registered new interface driver snd-usb-audio
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
ALSA device list:
  #0: TI81XX EVM
nf_conntrack version 0.5.0 (1898 buckets, 7592 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
Detected MACID=40:5f:c2:25:c5:cb
omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
ata1: SATA link down (SStatus 0 SControl 300)

CPSW phy found : id is : 0x1cc914

CPSW phy found : id is : 0x1cc914
IP-Config: Complete:
     device=eth0, addr=192.168.5.69, mask=255.255.255.0, gw=192.168.5.253,
     host=Z3-DM814x, domain=, nis-domain=(none),
     bootserver=192.168.5.101, rootserver=192.168.5.29, rootpath=
Waiting 4sec before mounting root device...
PHY: 0:01 - Link is Up - 0/Half
PHY: 0:01 - Link is Down
PHY: 0:00 - Link is Up - 100/Half
PHY: 0:01 - Link is Up - 100/Half
VFS: Mounted root (nfs filesystem) on device 0:15.
devtmpfs: mounted
Freeing init memory: 212K

INIT: version 2.86 booting

Error opening /dev/fb0: No such file or directory
Please wait: booting...
Starting udev
udevd (80): /proc/80/oom_adj is deprecated, please use /proc/80/oom_score_adj instead.
Root filesystem already rw, not remounting
Caching udev devnodes
ALSA: Restoring mixer settings...
NOT configuring network interfaces: / is an NFS mount
No state is present for card EVM
Found hardware: "" "" "" "" ""
Hardware is initialized using a generic method
No state is present for card EVM
Mon Apr 30 02:04:00 UTC 2012

INIT: Entering runlevel: 5

Loading HDVICP2 Firmware
DM814X prcm_config_app version: 2.0.0.1
Doing PRCM settings...
	PRCM for IVHD0 is in Progress, Please wait.....  
			BW Phy Addr : 0x48180600 Data : 0x00000001
			AW Phy Addr : 0x48180600 Data : 0x00000002
			Phy Addr : 0x48180c04 Data : 0x00000037
			BW Phy Addr : 0x48180620 Data : 0x00070000
			AW Phy Addr : 0x48180620 Data : 0x00070002
			BW Phy Addr : 0x48180624 Data : 0x00030000
			AW Phy Addr : 0x48180624 Data : 0x00010002
			Phy Addr : 0x48180600 Data : 0x00000102
			BW Phy Addr : 0x48180c10 Data : 0x00000007
			AW Phy Addr : 0x48180c10 Data : 0x00000003
			Phy Addr : 0x48180c14 Data : 0x00000004
			BW Phy Addr : 0x58088000 Data : 0xd95f55d9
			AW Phy Addr : 0x58088000 Data : 0xeafffffe
			BW Phy Addr : 0x58098000 Data : 0xb388a315
			AW Phy Addr : 0x58098000 Data : 0xeafffffe
			BW Phy Addr : 0x48180c10 Data : 0x00000003
			AW Phy Addr : 0x48180c10 Data : 0x00000000
			Phy Addr : 0x48180c14 Data : 0x00000007
	PRCM for IVHD0 is Done Successfully  
PRCM Initialization completed 
SysLink version : 2.10.03.20
SysLink module created on Date:Apr 30 2012 Time:01:23:00
FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
===Mandatory arguments=== 
<Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3 
<Location of Firmware> firmware binary file 
<start|stop>           to start/stop the firmware 
===Optional arguments=== 
-mmap                  input memory map bin file name 
-i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3 
FIRMWARE: isI2cInitRequiredOnM3: 1
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 1 start Successful
Loading HDVPSS Firmware
FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
===Mandatory arguments=== 
<Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3 
<Location of Firmware> firmware binary file 
<start|stop>           to start/stop the firmware 
===Optional arguments=== 
-mmap                  input memory map bin file name 
-i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3 
FIRMWARE: isI2cInitRequiredOnM3: 1
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 2 start Successful
Configuring fb0 to LCD
HDMI W1 rev 4.0
I2C No Ack


Starting system message bus: dbus.
Starting telnet daemon.
NET: Registered protocol family 10
Starting network benchmark server: netservernfs: server 192.168.5.29 not responding, still trying
nfs: server 192.168.5.29 not responding, still trying
------------[ cut here ]------------
WARNING: at net/sched/sch_generic.c:258 dev_watchdog+0x14c/0x234()
NETDEV WATCHDOG: eth0 (cpsw): transmit queue 0 timed out
Modules linked in: ipv6 tlc59108 ti81xxhdmi ti81xxfb vpss syslink
Backtrace: 
[<c004bbd0>] (dump_backtrace+0x0/0x110) from [<c03ef62c>] (dump_stack+0x18/0x1c)
 r7:c054be18 r6:c035e758 r5:c0516f70 r4:00000102
[<c03ef614>] (dump_stack+0x0/0x1c) from [<c006f6cc>] (warn_slowpath_common+0x54/0x6c)
[<c006f678>] (warn_slowpath_common+0x0/0x6c) from [<c006f788>] (warn_slowpath_fmt+0x38/0x40)
 r9:c05b8f8c r8:c05b938c r7:c054a000 r6:c05cc5ac r5:00000000
r4:c7973800
[<c006f750>] (warn_slowpath_fmt+0x0/0x40) from [<c035e758>] (dev_watchdog+0x14c/0x234)
 r3:c7973800 r2:c0516f88
[<c035e60c>] (dev_watchdog+0x0/0x234) from [<c0079fb8>] (run_timer_softirq+0x148/0x1e4)
 r6:c035e60c r5:00000100 r4:c05b8580
[<c0079e70>] (run_timer_softirq+0x0/0x1e4) from [<c0074858>] (__do_softirq+0x80/0x108)
[<c00747d8>] (__do_softirq+0x0/0x108) from [<c0074928>] (irq_exit+0x48/0x94)
[<c00748e0>] (irq_exit+0x0/0x94) from [<c003d080>] (asm_do_IRQ+0x80/0xa0)
[<c003d000>] (asm_do_IRQ+0x0/0xa0) from [<c03f1674>] (__irq_svc+0x34/0xa0)
Exception stack(0xc054bf48 to 0xc054bf90)
bf40:                   81400181 40000013 c054bf90 81400081 c054a000 c0597280
bf60: c00304a8 c054e0f4 80000000 413fc082 0000001f c054bf9c c054bf90 c054bf90
bf80: c0048f8c c0048f90 20000013 ffffffff
 r5:fa200000 r4:ffffffff
[<c0048f44>] (default_idle+0x0/0x54) from [<c0049534>] (cpu_idle+0x50/0x90)
[<c00494e4>] (cpu_idle+0x0/0x90) from [<c03e5fec>] (rest_init+0x60/0x78)
 r5:c0597280 r4:c05bb5a8
[<c03e5f8c>] (rest_init+0x0/0x78) from [<c0008cc4>] (start_kernel+0x270/0x2c8)
[<c0008a54>] (start_kernel+0x0/0x2c8) from [<80008048>] (0x80008048)
 r6:c00304a4 r5:c059739c r4:10c53c7d
---[ end trace 229e32a9cc35f113 ]---

  • Jakob,

    From the logs, its able to mount the NFS filesystem. But the server is not responding after some time. First you try to ping the server ip and see whether it is working. Also, could you please trying to mount the NFS from another board, with the same server when it is hung? 

    Also try setting ip=dhcp in bootargs and try? 

  • Renjith,


    Thank you for the response.


    I can successfully ping the NFS server while the boot process is hung. While I do not have another board to try NFS boot, I can mount and browse the NFS share on another machine while the boot process is hung. I tried using ip=dhcp, but then it attempts to continue the boot process from our DHCP server, which is different from the NFS server.

    A few more details on what I am trying to do:

    I have a board from Z3, and I am trying to use the kernel and root fs I built form the original TI EZSDK, essentially configured for the EVM. The above log is the issue I am getting. I can however successfully complete the boot process when I use the original kernel image provided by Z3 but with the TI EZSDK root fs over NFS. This makes me believe the issue is in the kernel configuration, but I am at a loss as to where specifically.

    Regards,

    Jakob 

  • Jakob,

    I don't have a Z3 board with me. But did you run the setup.sh script that comes with the EZSDK package? Also could you try using the prebuilt binaries that comes along with the EZSDK? Those images should work with NFS by default. I have tried those in the EVM before.