From: カオ ミン ヒェップ <cm-hiep@jinso.co.jp>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: netdev@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>
Subject: Ethernet bug at Upstream-v3.15-rcx on Lager.
Date: Thu, 15 May 2014 06:28:24 +0000 [thread overview]
Message-ID: <53745E88.7040108@jinso.co.jp> (raw)
Hi Sergei
I am Hiep from JINZAI SOLUTION (a Japanese Company).
Now, I am testing a upstream-v3.15-rc2 on Lager for Renesas RSO.
I found a problem about Ethernet Driver so I would like to report to you.
The problem is losing data when sending data by UDP:
- From Lager board to PC:
BANDWIDTH from 10M to 70M are good, but they suddenly down 51.2
Mbits/sec at 80M
and 57.8 Mbits/sec at 90 M and 64.2 Mbits/sec at 100M.
- From PC to Lager board:
Some time when the message of "sh-eth r8a7790-ether eth0: Receive
FIFO Overflow" occurs,
some of datagrams will be lost as the logs show below:
「$ iperf -c 172.16.1.36 -u -b 90M
.....
[ 3] Server Report:
[ 3] 0.0-10.0 sec 108 MBytes 90.4 Mbits/sec 0.000 ms
36/76923 (0.047%)
.....
# iperf -s -u
[ ID] Interval Transfer Bandwidth Jitter
Lost/Total Datagrams
sh-eth r8a7790-ether eth0: Receive FIFO Overflow
[ 3] 0.0-10.0 sec 108 MBytes 90.4 Mbits/sec 0.001 ms
36/76923 (0.047%)
Please review it when you have time.
Bests Regards,
Cao Minh Hiep.
WARNING: multiple messages have this Message-ID (diff)
From: カオ ミン ヒェップ <cm-hiep@jinso.co.jp>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: netdev@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>
Subject: Ethernet bug at Upstream-v3.15-rcx on Lager.
Date: Thu, 15 May 2014 15:28:24 +0900 [thread overview]
Message-ID: <53745E88.7040108@jinso.co.jp> (raw)
Hi Sergei
I am Hiep from JINZAI SOLUTION (a Japanese Company).
Now, I am testing a upstream-v3.15-rc2 on Lager for Renesas RSO.
I found a problem about Ethernet Driver so I would like to report to you.
The problem is losing data when sending data by UDP:
- From Lager board to PC:
BANDWIDTH from 10M to 70M are good, but they suddenly down 51.2
Mbits/sec at 80M
and 57.8 Mbits/sec at 90 M and 64.2 Mbits/sec at 100M.
- From PC to Lager board:
Some time when the message of "sh-eth r8a7790-ether eth0: Receive
FIFO Overflow" occurs,
some of datagrams will be lost as the logs show below:
「$ iperf -c 172.16.1.36 -u -b 90M
.....
[ 3] Server Report:
[ 3] 0.0-10.0 sec 108 MBytes 90.4 Mbits/sec 0.000 ms
36/76923 (0.047%)
.....
# iperf -s -u
[ ID] Interval Transfer Bandwidth Jitter
Lost/Total Datagrams
sh-eth r8a7790-ether eth0: Receive FIFO Overflow
[ 3] 0.0-10.0 sec 108 MBytes 90.4 Mbits/sec 0.001 ms
36/76923 (0.047%)
Please review it when you have time.
Bests Regards,
Cao Minh Hiep.
next reply other threads:[~2014-05-15 6:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 6:28 カオ ミン ヒェップ [this message]
2014-05-15 6:28 ` Ethernet bug at Upstream-v3.15-rcx on Lager カオ ミン ヒェップ
2014-05-15 17:20 ` Sergei Shtylyov
2014-05-15 17:20 ` Sergei Shtylyov
2014-05-16 1:08 ` カオ ミン ヒェップ
2014-05-16 1:08 ` カオ ミン ヒェップ
2014-05-16 5:56 ` Yoshihiro Shimoda
2014-05-16 5:56 ` Yoshihiro Shimoda
2014-05-30 14:04 ` Ben Dooks
2014-05-30 14:04 ` Ben Dooks
2014-06-03 2:43 ` Yoshihiro Shimoda
2014-06-03 2:43 ` Yoshihiro Shimoda
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=53745E88.7040108@jinso.co.jp \
--to=cm-hiep@jinso.co.jp \
--cc=horms@verge.net.au \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.