This is the mail archive of the
mailing list for the eCos project.
RE: Network code unstable (Solved).
- From: Gary Thomas <gthomas at redhat dot com>
- To: Pieter Truter <ptruter at intrinsyc dot com>
- Cc: eCos Disuss <ecos-discuss at sources dot redhat dot com>
- Date: 12 Feb 2002 12:16:05 -0700
- Subject: RE: [ECOS] Network code unstable (Solved).
- References: <FF4C56C7B8A3D41183FA000629D5CCACAE6B3F@cougar.intrinsyc.com>
On Tue, 2002-02-12 at 11:51, Pieter Truter wrote:
> I played around with my thread priority and made it 15 instead of 10. That
> solved my problem.
Is this [broken] testcase something you can share with me? I'd like to
understand the problems so we can fix them or document how to avoid them
like you have.
> For the record what should thead priorities be, not to interfere with the
> -----Original Message-----
> From: Andrew Lunn [mailto:email@example.com]
> Sent: Tuesday, February 12, 2002 10:33 AM
> To: Pieter Truter
> Cc: eCos Disuss
> Subject: Re: [ECOS] Network code unstable.
> On Tue, Feb 12, 2002 at 10:27:47AM -0800, Pieter Truter wrote:
> > This is only when I download big files (250Kb and up)
> The TFTP server has two different retry counters. For each 512byte
> packet it allows a number of retires and then gives up. Also, there is
> a maximum for the whole transfer. If you exceed either of these it
> closes the connection.
> Check for this. Maybe you are loosing packets or have a bad link?
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss