This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: ping is resulting in 50% packet loss.
- From: Gary Thomas <gary at chez-thomas dot org>
- To: George Sosnowski <george at stratalight dot com>
- Cc: eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Date: 22 Jul 2002 09:22:57 -0600
- Subject: RE: [ECOS] ping is resulting in 50% packet loss.
- References: <F626113795D3EB4482E5ACFBD9346512138314@mailhost.stratalight.com>
On Mon, 2002-07-22 at 09:20, George Sosnowski wrote:
> I had a similar problem when using the 860T fec driver initially.
> What it turned out to be was the IP stack or upper level networking code
> was calling fec_eth_start and fec_eth_init and both functions were
> setting the eConrtol_EN bit in the eControl byte. This was screwing up
> the state machine of the fec and causing it to act goofy. My work around
> for this was in fec_eth_start to check if eControl_EN was not enabled in
> the eControl byte before enabling it there.
>
> if(!(qi->fec->eControl & eControl_EN))
> {
> qi->fec->eControl |= eControl_EN;
> qi->fec->RxUpdate = 0x0f0f0f0f;
> }
>
This has been fixed in CVS for more than two months now.
> -----Original Message-----
> From: Khasim [mailto:khasim@iwavesystems.com]
> Sent: Sunday, July 21, 2002 9:19 PM
> To: ecos-discuss@sources.redhat.com
> Subject: [ECOS] ping is resulting in 50% packet loss.
>
> Greetings
>
> I saw same sort of question in the Discussion list but I didnt get the
> answer properly.
>
> I have ported the TCP/IP stack it is running from FLASH no redboot. When
> I
> ping from other windows machine to my boards ip address the ping is
> resulting in 60 or some times 50% packet loss.
>
> * I have not enabled any prints or debug messages.
> * But when I see in ethreal each packet is replied.
> * I dont know which TCP/IP stack I am using old or new.How to know
> this???
>
> Suggesstions please....
>
> With regards
> Khasim..
>
> Here is the output on cmd prompt
>
> C:\>ping -n 100 192.168.1.21
>
> Pinging 192.168.1.21 with 32 bytes of data:
>
> Request timed out.
> Request timed out.
> Reply from 192.168.1.21: bytes=32 time=501ms TTL=255
> Request timed out.
> Request timed out.
> Reply from 192.168.1.21: bytes=32 time=250ms TTL=255
> Reply from 192.168.1.21: bytes=32 time=250ms TTL=255
> Request timed out.
> Request timed out.
> Request timed out.
> Reply from 192.168.1.21: bytes=32 time=661ms TTL=255
> Request timed out.
> Request timed out.
> Reply from 192.168.1.21: bytes=32 time=821ms TTL=255
> Reply from 192.168.1.21: bytes=32 time=250ms TTL=255
> Request timed out.
> Request timed out.
> Reply from 192.168.1.21: bytes=32 time=251ms TTL=255
> Reply from 192.168.1.21: bytes=32 time=250ms TTL=255
> Request timed out.
> Request timed out.
> Reply from 192.168.1.21: bytes=32 time=251ms TTL=255
> Reply from 192.168.1.21: bytes=32 time=250ms TTL=255
> Request timed out.
> Request timed out.
> Reply from 192.168.1.21: bytes=32 time=250ms TTL=255
> Reply from 192.168.1.21: bytes=32 time=251ms TTL=255
> Request timed out.
> Request timed out.
> Reply from 192.168.1.21: bytes=32 time=250ms TTL=255
> Reply from 192.168.1.21: bytes=32 time=250ms TTL=255
> Request timed out.
> Request timed out.
> Reply from 192.168.1.21: bytes=32 time=251ms TTL=255
> Reply from 192.168.1.21: bytes=32 time=250ms TTL=255
> Request timed out.
> Request timed out.
>
> Ping statistics for 192.168.1.21:
> Packets: Sent = 40, Received = 16, Lost = 24 (60% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 250ms, Maximum = 821ms, Average = 130ms
> Control-C
>
>
> --
> 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
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss