use "ethtool eth#" to check your client and server ethernet card whether have the same speed. try the link http://nfs.sourceforge.net/nfs-howto/ar01s05.html and maybe help u. 5.8. Turning Off Autonegotiation of NICs and Hubs "if network cards auto-negotiate badly with hubs and switches, and ports run at different speeds, or with different duplex configurations, performance will be severely impacted due to excessive collisions, dropped packets, etc. If you see excessive numbers of dropped packets in the nfsstat output, or poor network performance in general, try playing around with the network speed and duplex settings. If possible, concentrate on establishing a 100BaseT full duplex subnet; the virtual elimination of collisions in full duplex will remove the most severe performance inhibitor for NFS over UDP. Be careful when turning off autonegotiation on a card: The hub or switch that the card is attached to will then resort to other mechanisms (such as parallel detection) to determine the duplex settings, and some cards default to half duplex because it is more likely to be supported by an old hub. The best solution, if the driver supports it, is to force the card to negotiate 100BaseT full duplex." 2010/1/30 Xiangfu Liu <xiangfu@xxxxxxxxxx>: > Hi > > I am not sure if this can help. > what's your switch. it's a switch or a hub. they are different in network > bandwidth. > in switch every port is 100MB but in hub all port will share 100MB. > just fyi. > Xiangfu > Best Regards > > Anuz Pratap Singh Tomar wrote: >> >> Hi all, >> I am trying to boot zoom2 board using tftpboot and nfs rootfs with >> following bootargs: >> >> console=ttyS3,115200n8 root=/dev/nfs rw >> nfsroot=192.168.25.1:/other_drive/targ >> et mem=256M devfs=mount >> >> In scenario 1. I have connected the board directly to eth1 of my machine, >> which runs a dhcp server. everything works fine, the board boots up. >> >> In scenario 2. I have connected a "network switch" between my eth1 and >> eth0 of board, board is able to boot the kernel but not able to mount nfs, >> Log message: server 192.168.25.1 not responding, still trying >> on sever side: >> tail -10 /var/log/messages: >> DHCPDISCOVER from 00:08:ee:03:7d:e7 via eth1 >> Jan 29 18:34:06 localhost dhcpd: DHCPOFFER on 192.168.25.12 to >> 00:08:ee:03:7d:e7 via eth1 >> Jan 29 18:34:06 localhost dhcpd: DHCPREQUEST for 192.168.25.12 >> (192.168.25.1) from 00:08:ee:03:7d:e7 via eth1 >> Jan 29 18:34:06 localhost dhcpd: DHCPACK on 192.168.25.12 to >> 00:08:ee:03:7d:e7 via eth1 >> >> now while looking around I came across some link which says, may be >> because of difference in speed of NIC of board and switch, so few of them >> directed to this link >> http://wiki.ltsp.org/twiki/bin/view/Ltsp/NFS#NFS_Server_not_responding >> >> however the above link is no more valid. >> >> >> I am not sure if introduction of network switch can create such error, I >> am able to nsfmount it from other machines in my network. >> Anyone has faced similar problem? >> >> >> >> Thanks >> Anuz >> >> > > > -- > To unsubscribe from this list: send an email with > "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx > Please read the FAQ at http://kernelnewbies.org/FAQ > > -- Best Regards Lin -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
