From: hayeswang <hayeswang@realtek.com>
To: 'Francois Romieu' <romieu@fr.zoreil.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH net-next] r8169: Remove rtl_ocpdr_cond
Date: Fri, 13 Jul 2012 11:17:59 +0800 [thread overview]
Message-ID: <33C8D1BCFFFF487FB7BC207EA9087C2E@realtek.com.tw> (raw)
In-Reply-To: <20120712221453.GA1982@electric-eye.fr.zoreil.com>
[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]
Francois Romieu [mailto:romieu@fr.zoreil.com]
[...]
>
> W/o firmware does not seem to make a difference.
>
> # ping -qf -l 4 -s 81 -c 60 10.0.3.1
> PING 10.0.3.1 (10.0.3.1) 81(109) bytes of data.
>
> --- 10.0.3.1 ping statistics ---
> 60 packets transmitted, 60 received, 0% packet loss, time 153ms
> rtt min/avg/max/mdev = 0.047/0.064/0.117/0.016 ms, pipe 4,
> ipg/ewma 2.607/0.058 ms
# ping -qf -l 4 -s 81 -c 60 192.168.94.20
PING 192.168.94.20 (192.168.94.20) 81(109) bytes of data.
--- 192.168.94.20 ping statistics ---
60 packets transmitted, 57 received, 5% packet loss, time 1ms
rtt min/avg/max/mdev = 0.028/0.040/0.101/0.011 ms, pipe 4, ipg/ewma 0.021/0.035
ms
> # ping -qf -l 4 -s 82 -c 60 10.0.3.1
>
> PING 10.0.3.1 (10.0.3.1) 82(110) bytes of data.
>
> --- 10.0.3.1 ping statistics ---
> 60 packets transmitted, 60 received, 0% packet loss, time 3ms
> rtt min/avg/max/mdev = 0.195/0.210/0.281/0.018 ms, pipe 4,
> ipg/ewma 0.057/0.205 ms
# ping -qf -l 4 -s 82 -c 60 192.168.94.20
PING 192.168.94.20 (192.168.94.20) 82(110) bytes of data.
--- 192.168.94.20 ping statistics ---
60 packets transmitted, 60 received, 0% packet loss, time 2ms
rtt min/avg/max/mdev = 0.151/0.173/0.247/0.020 ms, pipe 4, ipg/ewma 0.048/0.168
ms
> It would translate into a 127/128 cutoff after inclusion of the FCS.
>
> Any idea ?
>
The attatched file is my log. It seems fine.
[-- Attachment #2: a.log --]
[-- Type: application/octet-stream, Size: 2638 bytes --]
# ifconfig p33p1
p33p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.94.33 netmask 255.255.255.0 broadcast 192.168.94.255
inet6 fe80::2e0:4cff:fe68:ee1c prefixlen 64 scopeid 0x20<link>
ether 00:e0:4c:68:ee:1c txqueuelen 1000 (Ethernet)
RX packets 190 bytes 23670 (23.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 226 bytes 28381 (27.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
# ethtool -i p33p1
driver: r8169
version: 2.3LK-NAPI
firmware-version:
bus-info: 0000:04:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
# dmesg | tail -n 20
[ 15.091451] NET: Registered protocol family 31
[ 15.091454] Bluetooth: HCI device and connection manager initialized
[ 15.091457] Bluetooth: HCI socket layer initialized
[ 15.091460] Bluetooth: L2CAP socket layer initialized
[ 15.091466] Bluetooth: SCO socket layer initialized
[ 15.132905] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 15.132910] Bluetooth: BNEP filters: protocol multicast
[ 25.106009] em1: no IPv6 routers present
[ 45.489144] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 45.491423] r8169 0000:04:00.0: irq 47 for MSI/MSI-X
[ 45.491854] r8169 0000:04:00.0: eth0: RTL8168g/8111g at 0xf7e86000, 00:e0:4c:68:ee:1c, XID 0c000800 IRQ 47
[ 45.491859] r8169 0000:04:00.0: eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 45.767173] udevd[400]: renamed network interface eth0 to p33p1
[ 45.849390] r8169 0000:04:00.0: p33p1: unable to load firmware patch rtl_nic/rtl8168g-1.fw (-2)
[ 45.852564] r8169 0000:04:00.0: p33p1: link down
[ 45.852602] r8169 0000:04:00.0: p33p1: link down
[ 45.852743] ADDRCONF(NETDEV_UP): p33p1: link is not ready
[ 48.719667] r8169 0000:04:00.0: p33p1: link up
[ 48.719803] ADDRCONF(NETDEV_CHANGE): p33p1: link becomes ready
[ 59.330009] p33p1: no IPv6 routers present
# ping -qf -l 4 -s 81 -c 60 192.168.94.20
PING 192.168.94.20 (192.168.94.20) 81(109) bytes of data.
--- 192.168.94.20 ping statistics ---
60 packets transmitted, 57 received, 5% packet loss, time 1ms
rtt min/avg/max/mdev = 0.028/0.040/0.101/0.011 ms, pipe 4, ipg/ewma 0.021/0.035 ms
# ping -qf -l 4 -s 82 -c 60 192.168.94.20
PING 192.168.94.20 (192.168.94.20) 82(110) bytes of data.
--- 192.168.94.20 ping statistics ---
60 packets transmitted, 60 received, 0% packet loss, time 2ms
rtt min/avg/max/mdev = 0.151/0.173/0.247/0.020 ms, pipe 4, ipg/ewma 0.048/0.168 ms
next prev parent reply other threads:[~2012-07-13 3:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 12:31 [PATCH net-next] r8169: Remove rtl_ocpdr_cond Hayes Wang
2012-07-11 22:00 ` Francois Romieu
2012-07-12 22:14 ` Francois Romieu
2012-07-13 3:17 ` hayeswang [this message]
2012-07-17 10:10 ` 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=33C8D1BCFFFF487FB7BC207EA9087C2E@realtek.com.tw \
--to=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--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