NFS problem
hi all,
my 8270 board (2.4.26, u-boot 1.0.1, ELDK3.0) can't boot over NFS.
The messages are ..
=> bootm 100000
## Booting image at 00100000 ...
Image Name: Linux-2.4.26-rc2 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 723855 Bytes = 706.9 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Memory BAT mapping: BAT2=32Mb, BAT3=0Mb, residual: 0Mb
Linux version 2.4.26-rc2 (marco at linux) (gcc-Version 3.2.2 20030217 (Yellow Dog Linux 3.0 3.2.2-2a_1)) #2 Do Mai 27 08:48:15 CEST 2004 On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/nfs rw nfsroot=192.168.55.1:/opt/eldk_3_0/ppc_82xx ip=192.168.55.3:192.168.55.1::255.255.255.0:::off
Warning: real time clock seems stuck!
Calibrating delay loop... 131.89 BogoMIPS
Memory: 30624k available (1260k kernel code, 432k data, 56k init, 0k highmem)
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Installing knfsd (copyright (C) 1996 okir at monad.swb.de).
JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis Communications AB.
CPM UART driver version 0.01
ttyS0 on SCC1 at 0x8000, BRG1
ttyS1 on SCC2 at 0x8100, BRG2
pty: 256 Unix98 ptys configured
eth0: FCC ENET Version 0.3 , 00:11:22:73:44:55
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
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 2048 bind 4096)
IP-Config: Complete:
device=eth0, addr=192.168.55.3, mask=255.255.255.0, gw=255.255.255.255,
host=192.168.55.3, domain=, nis-domain=(none),
bootserver=192.168.55.1, rootserver=192.168.55.1, rootpath=NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.55.1
Looking up port of RPC 100005/1 on 192.168.55.1
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 56k init
INIT: version 2.84 booting
Welcome to DENX Embedded Linux Environment
Press 'I' to enter interactive startup.
Building the cache nfs: server 192.168.55.1 not responding, still trying
nfs: server 192.168.55.1 OK
nfs: server 192.168.55.1 not responding, still trying
nfs: server 192.168.55.1 OK
[ OK ]
Mounting proc filesystem:
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' than it hangs ...
sometimes it gets on a little bit, sometimes not...
Most time it hangs on "INIT: version 2.84 booting"
Any ideas ??
Why the "rootpath" isnt passed to the kernel?
Are the domain and nis-domain necessary for booting ?? With an initrd it works fine and i can ping the target and reverse.
Thanks for your ideas
Marco
---------
Marco Schramel
R&D
Bartec GmbH
Schulstr. 30
94239 Gotteszell, Germany
www.bartec.de
Marco.Schramel at go.bartec.de
Phone: +49 (0)9929/301332 Fax: +49 (0)9929/301112
Quoted 2 lines · In message <[email protected]> you wrote:
my 8270 board (2.4.26, u-boot 1.0.1, ELDK3.0) can't boot over NFS.
This is not really a U-Boot question, and thus off-topic here.
Quoted 1 line
Linux version 2.4.26-rc2 (marco at linux) (gcc-Version 3.2.2 20030217 (Yellow Dog Linux 3.0 3.2.2-2a_1)) #2 Do Mai 27 08:48:15 CEST 2004
Are you absolutely sure that this kernel is working as expected?
...
Quoted 4 lines
Building the cache nfs: server 192.168.55.1 not responding, still trying
nfs: server 192.168.55.1 OK
nfs: server 192.168.55.1 not responding, still trying
nfs: server 192.168.55.1 OK
...
Seems you have problems with your NFS server, and/or with your network interface - but tis can also mean that you just have the very common problem or incorrectly initialized SDRAM which fails when stress-tested in burst-mode by the network controller doing a lot of DMA.
Quoted 5 lines
than it hangs ...
sometimes it gets on a little bit, sometimes not... Most time it hangs on "INIT: version 2.84 booting"Any ideas ??
My bet is on SDRAM problems.
Quoted 1 line
Why the "rootpath" isnt passed to the kernel?
That's a bug in the Linux NFS code; just the messages are wrong. I tried to find out who is maintaining this code, but nobody seems to care.
Quoted 1 line
Are the domain and nis-domain necessary for booting ??
No.
Quoted 1 line
With an initrd it works fine and i can ping the target and reverse.
Try mounting a NFS filesystem in the initrd setup, or running a flood-ping with big packets, or run some other network benchmark (like netio or so). I guess then you will see the same problems.
Best regards,
Wolfgang Denk
Signature · 4 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de You have the capacity to learn from mistakes. You'll learn a lot today.