Skip to contentSkip to conversation

NFS and timeouts?

U-Boot Tom Rini 4 participants 7 messages Oct 13, 2016 – Oct 19, 2016

lore
Share & tools
lore

Tom Rini

author
#0 lore raw

Hey all,

I've noticed now, but not dug into a problem that goes like this. On every platform that I have tried NFS on now (and I wasn't a user before the test came in) I see:

# nfs 80000000 /tftpboot/1MiBtest.bin
link up on port 0, speed 1000, full duplex
#################################################################
         #################################################################
         #################################################################
         ##########T T T T
done
Bytes transferred = 1048576 (100000 hex)

for the same 1MiB file. The link line will vary from board to board but the end result is that I always see 4 T (for timeout) at the end of the transfer. On boards where I am doing this on gigabit the initial transfer is fast enough that the timeout doesn't cause failure. On the boards where I'm at 100Mbit instead however, I fail.

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161013/8d91101d/attachment.sig>
#1 lore raw

Hi Tom,

Quoted 14 lines · Tom Rini

Hey all,

I've noticed now, but not dug into a problem that goes like this. On every platform that I have tried NFS on now (and I wasn't a user before the test came in) I see:

# nfs 80000000 /tftpboot/1MiBtest.bin
link up on port 0, speed 1000, full duplex
#################################################################
         #################################################################
         #################################################################
         ##########T T T T
done
Bytes transferred = 1048576 (100000 hex)
Quoted 5 lines

for the same 1MiB file. The link line will vary from board to board but the end result is that I always see 4 T (for timeout) at the end of the transfer. On boards where I am doing this on gigabit the initial transfer is fast enough that the timeout doesn't cause failure. On the boards where I'm at 100Mbit instead however, I fail.

I have seen this also - what type of interface are you using?

Regards,
Simon

#2 lore raw
Quoted 17 lines · Simon Glass

Hi Tom,

Quoted 14 lines · Tom Rini

Hey all,

I've noticed now, but not dug into a problem that goes like this. On every platform that I have tried NFS on now (and I wasn't a user before the test came in) I see:

# nfs 80000000 /tftpboot/1MiBtest.bin
link up on port 0, speed 1000, full duplex
#################################################################
         #################################################################
         #################################################################
         ##########T T T T
done
Bytes transferred = 1048576 (100000 hex)
Quoted 7 lines
Quoted 5 lines

for the same 1MiB file. The link line will vary from board to board but the end result is that I always see 4 T (for timeout) at the end of the transfer. On boards where I am doing this on gigabit the initial transfer is fast enough that the timeout doesn't cause failure. On the boards where I'm at 100Mbit instead however, I fail.

I have seen this also - what type of interface are you using?

Does this happen in your testing, Guillaume?

#3 lore raw

Hi,

Le 14/10/2016 ? 01:00, Joe Hershberger a ?crit :

Quoted 18 lines · Simon Glass
Quoted 17 lines

Hi Tom,

Quoted 14 lines · Tom Rini

Hey all,

I've noticed now, but not dug into a problem that goes like this. On every platform that I have tried NFS on now (and I wasn't a user before the test came in) I see:

# nfs 80000000 /tftpboot/1MiBtest.bin
link up on port 0, speed 1000, full duplex
#################################################################
          #################################################################
          #################################################################
          ##########T T T T
done
Bytes transferred = 1048576 (100000 hex)
Quoted 8 lines
Quoted 6 lines
Quoted 5 lines

for the same 1MiB file. The link line will vary from board to board but the end result is that I always see 4 T (for timeout) at the end of the transfer. On boards where I am doing this on gigabit the initial transfer is fast enough that the timeout doesn't cause failure. On the boards where I'm at 100Mbit instead however, I fail.

I have seen this also - what type of interface are you using?

Does this happen in your testing, Guillaume?

No, I never saw those timeouts. I will try to reproduce here. On which boards does it happen?

Guillaume

author
#4 lore raw
Quoted 27 lines · Guillaume Gardet

Hi,

Le 14/10/2016 ? 01:00, Joe Hershberger a ?crit :

Quoted 23 lines · Simon Glass
Quoted 22 lines

Hi Tom,

Quoted 19 lines · Tom Rini

Hey all,

I've noticed now, but not dug into a problem that goes like this. On every platform that I have tried NFS on now (and I wasn't a user before the test came in) I see:

# nfs 80000000 /tftpboot/1MiBtest.bin
link up on port 0, speed 1000, full duplex
#################################################################
         #################################################################
         #################################################################
         ##########T T T T
done
Bytes transferred = 1048576 (100000 hex)

for the same 1MiB file. The link line will vary from board to board but the end result is that I always see 4 T (for timeout) at the end of the transfer. On boards where I am doing this on gigabit the initial transfer is fast enough that the timeout doesn't cause failure. On the boards where I'm at 100Mbit instead however, I fail.

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

I have seen this also - what type of interface are you using?

Does this happen in your testing, Guillaume?

No, I never saw those timeouts. I will try to reproduce here. On which boards does it happen?

AM335x GP EVM, DRA72x EVM ("J6 Eco"), Beagleboard xM, RPi 3 (32 or 64bit mode). I suspect it's something either config or network related. Everything is on the same 24 port gigabit switch.

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161014/b3db8416/attachment.sig>
#5 lore raw

Hi,

Le 14/10/2016 ? 15:40, Tom Rini a ?crit :

Quoted 28 lines · Guillaume Gardet
Quoted 27 lines

Hi,

Le 14/10/2016 ? 01:00, Joe Hershberger a ?crit :

Quoted 23 lines · Simon Glass
Quoted 22 lines

Hi Tom,

Quoted 19 lines · Tom Rini

Hey all,

I've noticed now, but not dug into a problem that goes like this. On every platform that I have tried NFS on now (and I wasn't a user before the test came in) I see:

# nfs 80000000 /tftpboot/1MiBtest.bin
link up on port 0, speed 1000, full duplex
#################################################################
          #################################################################
          #################################################################
          ##########T T T T
done
Bytes transferred = 1048576 (100000 hex)

for the same 1MiB file. The link line will vary from board to board but the end result is that I always see 4 T (for timeout) at the end of the transfer. On boards where I am doing this on gigabit the initial transfer is fast enough that the timeout doesn't cause failure. On the boards where I'm at 100Mbit instead however, I fail.

Quoted 9 lines
Quoted 5 lines
Quoted 3 lines
Quoted 1 line

I have seen this also - what type of interface are you using?

Does this happen in your testing, Guillaume?

No, I never saw those timeouts. I will try to reproduce here. On which boards does it happen?

AM335x GP EVM, DRA72x EVM ("J6 Eco"), Beagleboard xM, RPi 3 (32 or 64bit mode). I suspect it's something either config or network related. Everything is on the same 24 port gigabit switch.

I just tried 2016.11-rc2 on a Beagleboard xM with:
* nfs download from a NFSv2 server
* nfs download from a NFSv3 server
* tftpboot download from a TFTP server

And all are working fine here.

Guillaume

author
#6 lore raw
In reply to Simon Glass
Quoted 17 lines · Simon Glass

Hi Tom,

Quoted 14 lines · Tom Rini

Hey all,

I've noticed now, but not dug into a problem that goes like this. On every platform that I have tried NFS on now (and I wasn't a user before the test came in) I see:

# nfs 80000000 /tftpboot/1MiBtest.bin
link up on port 0, speed 1000, full duplex
#################################################################
         #################################################################
         #################################################################
         ##########T T T T
done
Bytes transferred = 1048576 (100000 hex)
Quoted 7 lines
Quoted 5 lines

for the same 1MiB file. The link line will vary from board to board but the end result is that I always see 4 T (for timeout) at the end of the transfer. On boards where I am doing this on gigabit the initial transfer is fast enough that the timeout doesn't cause failure. On the boards where I'm at 100Mbit instead however, I fail.

I have seen this also - what type of interface are you using?

I see it on CPSW (am335x, dra7xx) and the USB smsc95xx on rpi3 and the USB ASIX on omap3_beagle.

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161013/6e9e9954/attachment.sig>