NFS trouble?



I could use some help figuring out this problem. I am bringing-up a
Freescale M5373EVB board. The documentation included with the uCLinux
BSP is flawed in many ways and had made it a very time consuming
task. I finally got it going only to have it hang shortly after it
seems to mount the NFS root. Here's the output from minicom:

dBUG> show
base: 16
baud: 115200
autoboot: Stop at prompt
server: 192.168.0.5
client: 192.168.0.50
gateway: 192.168.0.1
netmask: 255.255.255.0
filename: vmlinux.bin
filetype: Image
ethaddr: 00:CF:53:73:CF:01
kcl: root=/dev/nfs rw nfsroot=192.168.0.5:/tftpboot/ltib
ip=192.168.0.50:192.168.0.5:192.168.0.1:255.255.255.0::eth0:off
dBUG> dn
Downloading Image 'vmlinux.bin' from 192.168.0.5
TFTP transfer completed
Read 1990656 bytes (3889 blocks)
dBUG> go 0x40020000
Linux version 2.6.22-uc1 (mattw@loa) (gcc version 4.2.1 (Sourcery G++
Lite 4.2-47)) #1 Fri Nov 9 09:40:36 MST 2007


uClinux/COLDFIRE(m537x)
COLDFIRE port done by Greg Ungerer, gerg@xxxxxxxxxxxx
Flat model support (C) 1998,1999 Kenneth Albanowski, D. Jeff Dionne
Built 1 zonelists. Total pages: 8128
Kernel command line: root=/dev/nfs rw nfsroot=192.168.0.5:/tftpboot/
ltib ip=192.168.0.50:192.168.0.5:192.168.0.1:255.255.255.0::eth0:off
PID hash table entries: 128 (order: 7, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory available: 30308k/32768k RAM, (1788k kernel code, 244k data)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
USB-MCF537x: (HOST module) EHCI device is registered
USB-MCF537x: (OTG module) EHCI device is registered
USB-MCF537x: (OTG module) UDC device is registered
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
JFFS2 version 2.2. (NAND) .. 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler cfq registered (default)
ColdFire internal UART serial driver version 1.00
ttyS0 at 0xfc060000 (irq = 90) is a builtin ColdFire UART
ttyS1 at 0xfc064000 (irq = 91) is a builtin ColdFire UART
ttyS2 at 0xfc068000 (irq = 92) is a builtin ColdFire UART
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: module loaded
nbd: registered device at major 43
usbcore: registered new interface driver ub
FEC ENET Version 0.2
fec: PHY @ 0x1, ID 0x20005c90 -- DP83848
eth0: ethernet 00:cf:53:73:cf:01
uclinux[mtd]: RAM probe address=0x4021c22c size=0x401000
Creating 1 MTD partitions on "RAM":
0x00000000-0x00401000 : "ROMfs"
uclinux[mtd]: set ROMfs to be root filesystem
NAND device: Manufacturer ID: 0x20, Chip ID: 0x73 (ST Micro NAND 16MiB
3,3V 8-bit)
Scanning device for bad blocks
Creating 1 MTD partitions on "NAND 16MiB 3,3V 8-bit":
0x00000000-0x01000000 : "M53xx flash partition 1"
QSPI: spi->max_speed_hz 300000
QSPI: Baud set to 255
SPI: Coldfire master initialized
M537x - Disable UART1 when using Audio
udc: Freescale MCF53xx UDC driver version 27 October 2006 init
udc: MCF53xx USB Device is found. ID=0x5 Rev=0x41
i2c /dev entries driver
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
IP-Config: Complete:
device=eth0, addr=192.168.0.50, mask=255.255.255.0,
gw=192.168.0.1,
host=192.168.0.50, domain=, nis-domain=(none),
bootserver=192.168.0.5, rootserver=192.168.0.5, rootpath=
Looking up port of RPC 100003/2 on 192.168.0.5
Looking up port of RPC 100005/1 on 192.168.0.5
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 64k freed (0x401f5000 - 0x40204000)
nfs: server 192.168.0.5 not responding, still trying
nfs: server 192.168.0.5 OK
nfs: server 192.168.0.5 not responding, still trying
nfs: server 192.168.0.5 OK
....
This continues nonstop. It never gets to a command prompt. This is
my first uClinux project (and the first time back to Linux in a long
time (last time I played with Linux it was version 1.4 or so) and I'm
a little confused as to what might be going on here.

BTW, I verified that NFS is working by mounting it locally with:
mount -t nfs localhost:...etc, etc.

Thanks,

-Martin


.



Relevant Pages

  • Re: Gianfar driver failing on MPC8641D based board
    ... The boot process grinds to a halt not long after the first access of the ... NFS root and I receive multiple "nfs: server 192.168.0.1 not responding, ... at which point the gianfar network driver fails to compile (I have tried ...
    (Linux-Kernel)
  • Re: Gianfar driver failing on MPC8641D based board
    ... NFS root and I receive multiple "nfs: server 192.168.0.1 not responding, ... at which point the gianfar network driver fails to compile (I have tried ... registered new interface driver hub ...
    (Linux-Kernel)
  • Re: 2008 SBS no longer boots
    ... Intel raid card for Server 2003. ... install with one raid driver, or with the other raid driver. ... Any thermal issues and a lot of other hardware problems should show up ... other customer, even a 2 week old one, the problem immediately returned. ...
    (microsoft.public.windows.server.sbs)
  • core install of Solaris 9 (sparc) package list can be trimmed ?
    ... This is a server that will have very specific reasons ... system SUNWadmr System & Network Administration Root ... system SUNWeu8os American English/UTF-8 L10N For OS Environment User Files ... system R SUNWfcip Sun FCIP IP/ARP over FibreChannel Device Driver ...
    (comp.unix.solaris)
  • Re: 2008 SBS no longer boots
    ... driver issue initially, the fact that it seems to happen randomly now ... weird with a hardware problem that consistently doesn't get through boot ... other customer, even a 2 week old one, the problem immediately returned. ... There was a time when a server was fired up with a specialized OS and had a battery of tests run against each component to purposefully stress it. ...
    (microsoft.public.windows.server.sbs)