Comment 5 for bug 1900773

Revision history for this message
dann frazier (dannf) wrote : Re: [Bug 1900773] Re: thunderx CRB systems tftp timeout downloading initrd

On Tue, Oct 20, 2020 at 5:30 PM Steve Langasek
<email address hidden> wrote:
>
> And is there something intrinsic to this hardware that leads to the
> timeout?

I wonder if there might be a firmware bug. Here's what I see on the wire:

52120 56.958016 10.229.50.135 10.229.50.84 TFTP 78 Read Request, File:
initrd, Transfer type: octet, blksize=1024, tsize=0
52121 56.960144 10.229.50.84 10.229.50.135 TFTP 72 Option
Acknowledgement, blksize=1024, tsize=90771321
<---snip--->
183218 65.602857 10.229.50.84 10.229.50.135 TFTP 1070 Data Packet, Block: 65535
183219 65.603129 10.229.50.135 10.229.50.84 TFTP 60 Acknowledgement,
Block: 65535
<---snip--->
229458 68.561417 10.229.50.135 10.229.50.84 TFTP 60 Acknowledgement,
Block: 88643
229459 68.561466 10.229.50.84 10.229.50.135 TFTP 935 Data Packet,
Block: 88644 (last)
229460 68.561519 10.229.50.135 10.229.50.84 TFTP 60 Acknowledgement,
Block: 88644
229462 68.962413 10.229.50.135 10.229.50.84 TFTP 60 Acknowledgement,
Block: 65535

It looks like the entire initrd was successfully transferred. The
client ACK'd the last block but then, for some reason, it comes back
about half a second later and re-ACKs a block it had already ACK'd.
And that block being number number 65535 is *interesting*.

> Or would this perhaps work if the machine had a faster network
> link to the tftp server?

Perhaps - but these systems are in the same physical location, slowest
link between is 1Gbps.