From: Nolwenn <donolwenn@gmail.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: hayeswang <hayeswang@realtek.com>, netdev@vger.kernel.org
Subject: Re: Possible bug with r8169 driver
Date: Fri, 28 Sep 2012 06:47:06 +0000 [thread overview]
Message-ID: <1478421.GOy9qdQlkG@bureau> (raw)
In-Reply-To: <20120927222147.GA29047@electric-eye.fr.zoreil.com>
Le vendredi 28 septembre 2012 00:21:47 Francois Romieu a écrit :
> Can you send an 'ip -s link' before any ipv6 traffic flows, then
> after ?
>
Before ipv6 traffic
% ip -s link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
RX: bytes packets errors dropped overrun mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP mode DEFAULT qlen 1000
link/ether 30:85:a9:ee:43:fa brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
2607155 2232 0 0 0 0
TX: bytes packets errors dropped carrier collsns
142314 1725 0 0 0 0
During tcpdump interception
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
RX: bytes packets errors dropped overrun mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP mode DEFAULT qlen 1000
link/ether 30:85:a9:ee:43:fa brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
4191544 4587 0 0 0 0
TX: bytes packets errors dropped carrier collsns
268787 3317 0 0 0 0
After set set eth0 in promisc mode
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
RX: bytes packets errors dropped overrun mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
2: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UP mode DEFAULT qlen 1000
link/ether 30:85:a9:ee:43:fa brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
10301337 12212 0 0 0 0
TX: bytes packets errors dropped carrier collsns
803894 9309 0 0 0 0
> > % dmesg | grep r8169
> >
> > [ 1.810423] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
> > [ 1.810548] r8169 0000:03:00.0: irq 44 for MSI/MSI-X
> > [ 1.810671] r8169 0000:03:00.0: eth0: RTL8168f/8111f at
> > 0xffffc900057ae000, 30:85:a9:ee:43:fa, XID 08000800 IRQ 44 [ 1.810672]
> > r8169 0000:03:00.0: eth0: jumbo features [frames: 9200 bytes, tx
> > checksumming: ko]
> Hayes, is there by any luck something different for the 8168f regarding
> the layout of the multicast filtering registers ?
I don't have sufficient skills in networks to understand what do you mean,
sorry. Any command line, files comparing to get the information?
next prev parent reply other threads:[~2012-09-28 6:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 14:24 Possible bug with r8169 driver Nolwenn
2012-09-27 22:21 ` Francois Romieu
2012-09-28 6:47 ` Nolwenn [this message]
2012-09-29 7:20 ` Francois Romieu
2012-09-29 14:49 ` Nolwenn
2012-09-29 19:01 ` Francois Romieu
2012-09-30 19:17 ` Nolwenn
2012-10-01 5:51 ` hayeswang
2012-10-01 18:56 ` Francois Romieu
2012-10-04 2:09 ` hayeswang
2012-11-07 9:54 ` Nolwenn
2012-11-07 19:06 ` Francois Romieu
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=1478421.GOy9qdQlkG@bureau \
--to=donolwenn@gmail.com \
--cc=hayeswang@realtek.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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