Have you done the nfs start in the booting kernel ?? On Tue, 2003-01-21 at 19:41, ramprasad wrote: > Hello All, > > When I load the Kernel into my target board. I got the following message and > I am not able to mount NFS file system. > > > IP-Config: Complete: > device=eth0, addr=10.72.148.8, mask=255.255.248.0, gw=10.72.149.201, > host=target02, domain=, nis-domain=(none), > bootserver=10.72.149.201, rootserver=10.72.149.201, rootpath= > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. > Looking up port of RPC 100003/3 on 10.72.149.201 > NETDEV WATCHDOG: eth0: transmit timed out > eth0: transmit timed out, status 0073, resetting. > portmap: server 10.72.149.201 not responding, timed out > Root-NFS: Unable to get nfsd port number from server, using default > Looking up port of RPC 100005/3 on 10.72.149.201 > portmap: server 10.72.149.201 not responding, timed out > Root-NFS: Unable to get mountd port number from server, using default > NETDEV WATCHDOG: eth0: transmit timed out > eth0: transmit timed out, status 0073, resetting. > NETDEV WATCHDOG: eth0: transmit timed out > eth0: transmit timed out, status 0073, resetting. > mount: server 10.72.149.201 not responding, timed out > Root-NFS: Server returned error -5 while mounting /work/nfsroot0723 > VFS: Unable to mount root fs via NFS, trying floppy. > VFS: Cannot open root device "nfs" or 02:00 > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on 02:00 > > What could be the problem, where I am doing the mistake. (I did not enable > WATCHDOG, still I am getting WATCHDOG errors) > > I tested a different working kernel with same NFS Server settings and > command line arguments, it is working fine. > > Thanks in advance > > Regards > Ramprasad > > > > > > > > > > > > > portmap: server 10.72.149.201 not responding, timed out > Root-NFS: Unable to get mountd port number from server, using default > Linux version 2.4.9-13.am33-020219 (root@px6123) (gcc version > 3.1-am33-020219) #2 Fri Jan 17 13:24:36 EST 2003 > On node 0 totalpages: 16384 > zone(0): 0 pages. > zone(1): 16384 pages. > zone(2): 0 pages. > Kernel command line: mem=64M root=/dev/nfs console=ttyS0,115200 > nfsroot=10.72.149.201:/work/nfsroot0723,v3 > ip=10.72.148.8:10.72.149.201:10.72.149.201:255.255.248.0:target02:eth0:off > Calibrating delay loop... 65.74 BogoMIPS > Memory: 62508k/65536k available (1064k kernel code, 0k reserved, 52k data, > 152k init, 0k highmem) > Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes) > Inode-cache hash table entries: 4096 (order: 3, 32768 bytes) > Mount-cache hash table entries: 1024 (order: 1, 8192 bytes) > super.c > Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes) > Page-cache hash table entries: 16384 (order: 5, 131072 bytes) > super.c > POSIX conformance testing by UNIFIX > PCI: Using configuration ampci > PCI: Probing PCI hardware > Scanning bus 00 > Found 00:00 [1189/283c] 000600 00 > Found 00:10 [1022/2000] 000200 00 > Found 00:18 [1011/0022] 000604 01 > Fixups for bus 00 > Scanning behind PCI bridge 00:03.0 > Scanning bus 01 > Found 01:78 [1113/1216] 000200 00 > Fixups for bus 01 > Bus scan for 01 returning with max=01 > Bus scan for 00 returning with max=01 > PCI: Cannot allocate resource region 0 of device 00:00.0 > Linux NET4.0 for Linux 2.4 > Based upon Swansea University Computer Society NET3.039 > super.c > Starting kswapd v1.8 > super.c > super.c > super.c > devfs: v0.107 (20010709) Richard Gooch (rgooch@atnf.csiro.au) > devfs: boot_options: 0x0 > super.c > pty: 256 Unix98 ptys configured > Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ > SERIAL_PCI enabled > ttyS00 at 0x0000 (irq = 34) is a 16550A > ttyS01 at 0x0000 (irq = 0) is a 16450 > block: queued sectors max/low 41469kB/13823kB, 128 slots per queue > RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize > pcnet32_probe_pci: found device 0x001022.0x002000 > PCI: Enabling device 00:02.0 (0000 -> 0003) > PCI: Enabling bus mastering for device 00:02.0 > PCI: Setting latency timer of device 00:02.0 to 64 > ioaddr=0x001000 resource_flags=0x000101 > pcnet32: PCnet/FAST III 79C973 at 0x1000, 00 80 45 16 00 70 > pcnet32: pcnet32_private lp=90456000 lp_dma_addr=0x90456000 assigned IRQ 35. > pcnet32.c:v1.25kf 26.9.1999 tsbogend@alpha.franken.de > pcnet32: registered as eth0 > PPP generic driver version 2.4.1 > PPP Deflate Compression module registered > PPP BSD Compression module registered > NET4: Linux TCP/IP 1.0 for NET4.0 > IP Protocols: ICMP, UDP, TCP > IP: routing cache hash table of 512 buckets, 4Kbytes > TCP: Hash tables configured (established 4096 bind 8192) > IP-Config: Complete: > device=eth0, addr=10.72.148.8, mask=255.255.248.0, gw=10.72.149.201, > host=target02, domain=, nis-domain=(none), > bootserver=10.72.149.201, rootserver=10.72.149.201, rootpath= > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. > Mounting Root Before > super.c > Looking up port of RPC 100003/3 on 10.72.149.201 > NETDEV WATCHDOG: eth0: transmit timed out > eth0: transmit timed out, status 0073, resetting. > portmap: server 10.72.149.201 not responding, timed out > Root-NFS: Unable to get nfsd port number from server, using default > Looking up port of RPC 100005/3 on 10.72.149.201 > portmap: server 10.72.149.201 not responding, timed out > Root-NFS: Unable to get mountd port number from server, using default > NETDEV WATCHDOG: eth0: transmit timed out > eth0: transmit timed out, status 0073, resetting. > NETDEV WATCHDOG: eth0: transmit timed out > eth0: transmit timed out, status 0073, resetting. > mount: server 10.72.149.201 not responding, timed out > Root-NFS: Server returned error -5 while mounting /work/nfsroot0723 > VFS: Unable to mount root fs via NFS, trying floppy. > VFS: Cannot open root device "nfs" or 02:00 > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on 02:00 > > > -- > Kernelnewbies: Help each other learn about the Linux kernel. > Archive: http://mail.nl.linux.org/kernelnewbies/ > FAQ: http://kernelnewbies.org/faq/ > > -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
