From: "Aníbal Almeida Pinto" <anibal.pinto@efacec.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: Gianfar ethernet drop package
Date: Mon, 27 Aug 2012 11:32:27 +0100 [thread overview]
Message-ID: <503B4CBB.1020405@efacec.com> (raw)
In-Reply-To: <1345832223.19483.75.camel@edumazet-glaptop>
Em 24-08-2012 19:17, Eric Dumazet escreveu:
> On Fri, 2012-08-24 at 17:14 +0100, Aníbal Almeida Pinto wrote:
>> Hi,
>>
>> I have an board with a ppc with a 8379, kernel 3.0.39 and with a Gianfar
>> Ethernet Controller Version 1.2.
>>
>> When connect the board to office network the number of dropped packets
>> reported by ifconfig continues to increase.
>>
>> Following the test made at [1] I use tcpdump and when running it the
>> number of drop packages don't have increased.
>>
>> When executing ethtool eth0 -S it return a rx-dropped-by-kernel != 0.
>> And the rest of drop packages
>>
>> Is possible to get info why the packages are dropped?
>
> You receive frames for unknown protocols. So they are dropped.
>
> When running tcpdump, your tcpdump get them, they are not dropped.
>
> So just parse your tcpdump output ?
>
I generate the log on the board with tcpdump -i eth0 -w log_eth0.txt and
loaded the result on wireshark (on other pc).
On the wireshark everything appears to be fine don't have nothing that
indicate the protocol isn't supported.
On /etc/protocols is a list with protocols, it there is a place where
exist a place with protocols supported by kernel ?
Thanks
next prev parent reply other threads:[~2012-08-27 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 16:14 Gianfar ethernet drop package Aníbal Almeida Pinto
2012-08-24 18:17 ` Eric Dumazet
2012-08-27 10:32 ` Aníbal Almeida Pinto [this message]
2012-08-27 11:08 ` Eric Dumazet
2012-08-27 13:01 ` Aníbal Almeida Pinto
2012-08-27 13:32 ` Eric Dumazet
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=503B4CBB.1020405@efacec.com \
--to=anibal.pinto@efacec.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).