public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] commit 620776d causes TFTP error: 'Unsupported option(s) requested' (8)
Date: Tue, 25 Aug 2015 13:28:13 +0200	[thread overview]
Message-ID: <20150825112812.GA15642@amd> (raw)
In-Reply-To: <CAEUhbmXywZuAe9rQMiDpHaAS2O6K8gSwhM1CSckmGUNyb_qhVQ@mail.gmail.com>

On Tue 2015-08-25 16:58:58, Bin Meng wrote:
> Hi Pavel,
> 
> On Tue, Aug 25, 2015 at 3:12 PM, Pavel Machek <pavel@denx.de> wrote:
> > On Tue 2015-08-25 10:25:35, Bin Meng wrote:
> >> Hi,
> >>
> >> With latest u-boot/master, TFTP is seriously broken.
> >
> > Sorry about that.
> >
> >> => tftp 100000 bzImage
> >> Speed: 100, full duplex
> >> Using pch_gbe device
> >> TFTP from server 10.10.0.8; our IP address is 10.10.0.100; sending
> >> through gateway 10.10.0.1
> >> Filename 'bzImage'.
> >> Load address: 0x100000
> >> Loading: T
> >> TFTP error: 'Unsupported option(s) requested' (8)
> >> Starting again
> >>
> >> git bisect shows the following commit broke the TFTP
> >
> > I was not intentionally changing the packets being sent.
> >
> > Could you try to capture tcpdump, including contents of packet,
> > ideally in both working and broken sessions?
> >
> 
> Yep, I will do that. I also tested a tftpd Windows server
> (http://tftpd32.jounin.net) and it looks that this Windows server is
> immune to this commit.
> 
> > Could you try setting
> >
> > -#define TIMEOUT                5000UL
> > +#define TIMEOUT                100UL
> >
> > in net/tftp.c to something like 1000UL?
> >
> 
> Could you please elaborate more on what this commit is trying to fix,
> or improve? From the commit message, I don't quite understand "With 5
> seconds timeout, 10 retries maximum, tftp is impossible even on local
> network with single full-speed TCP connection".

Well, with 10 retries maximum, I get enough packet loss on local
network that tftp fails.

Now, longer timeout will make it slower, but not fail. So "max
retries" is really critical.

If rfc says minimum is 1sec, we should not really default to 100msec,
sorry about that. Can you try with 1sec if it works for you?

Thanks and best regards,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2015-08-25 11:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25  2:25 [U-Boot] commit 620776d causes TFTP error: 'Unsupported option(s) requested' (8) Bin Meng
2015-08-25  3:42 ` Joe Hershberger
2015-08-25  4:05   ` Bin Meng
2015-08-25  4:24     ` Joe Hershberger
2015-08-25  7:40       ` Bin Meng
2015-08-25 12:13         ` Hannes Schmelzer
2015-08-25 12:19           ` Pavel Machek
2015-08-25 12:23             ` Hannes Schmelzer
2015-09-10 22:26             ` Alexey Brodkin
2015-09-10 22:46               ` Joe Hershberger
2015-09-10 22:51               ` Simon Glass
2015-08-25  7:12 ` Pavel Machek
2015-08-25  8:58   ` Bin Meng
2015-08-25  9:22     ` Bin Meng
2015-08-25 11:28     ` Pavel Machek [this message]
2015-08-25 11:44     ` [U-Boot] [PATCH] Change default tftp timeout to be rfc-compliant Pavel Machek
2015-08-25 13:03       ` Bin Meng
2015-08-25 14:32         ` Pavel Machek
2015-08-25 14:49           ` Tom Rini
2015-08-25 15:33             ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150825112812.GA15642@amd \
    --to=pavel@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox