From: peppe.cavallaro@st.com (Giuseppe CAVALLARO)
To: linus-amlogic@lists.infradead.org
Subject: stmmac/RTL8211F/Meson GXBB: TX throughput problems
Date: Mon, 26 Sep 2016 08:17:50 +0200 [thread overview]
Message-ID: <d59f6e2c-15ff-779d-da2f-8eb5f5a535a6@st.com> (raw)
In-Reply-To: <20160917232312.1e30d425@gmail.com>
Hello Andr?
On 9/17/2016 11:23 PM, Andr? Roth wrote:
>
> Hi all,
>
> I have an odroid c2 board which shows this issue. No data is
> transmitted or received after a moment of intense tx traffic. Copying a
> 1GB file per scp from the board triggers it repeatedly.
>
> The board has a stmmac - user ID: 0x11, Synopsys ID: 0x37.
>
> When switching the network to 100Mb/s the copying does
> not seam to trigger the issue.
>
> I've attached the ethtool statistics before and after the problem.
at first glance, it enters in EEE mode often in the ethtool.after.
On some platforms we met problems and it was necessary to disable the
feature. Maybe, you can start looking at if this is true on yours.
We will see to provide a clean subset of patches to switch-on/off it.
Peppe
>
> Thanks for your help,
>
> Andr?
>
>
>
>> Hi Alexandre,
>>
>> On Mon, Sep 12, 2016 at 6:37 PM, Alexandre Torgue
>> <alexandre.torgue@st.com> wrote:
>>> Which Synopsys IP version do you use ?
>> found this in a dmesg log:
>> [ 1.504784] stmmac - user ID: 0x11, Synopsys ID: 0x37
>> [ 1.509785] Ring mode enabled
>> [ 1.512796] DMA HW capability register supported
>> [ 1.517286] Normal descriptors
>> [ 1.520565] RX Checksum Offload Engine supported
>> [ 1.525219] COE Type 2
>> [ 1.527638] TX Checksum insertion supported
>> [ 1.531862] Wake-Up On Lan supported
>> [ 1.535483] Enable RX Mitigation via HW Watchdog Timer
>> [ 1.543851] libphy: stmmac: probed
>> [ 1.544025] eth0: PHY ID 001cc916 at 0 IRQ POLL (stmmac-0:00)
>> active [ 1.550321] eth0: PHY ID 001cc916 at 7 IRQ POLL
>> (stmmac-0:07)
>>
>>>> Gbit ethernet on my device is provided by a Realtek RTL8211F RGMII
>>>> PHY. Similar issues were reported in #linux-amlogic by a user with
>>>> an Odroid C2 board (= similar hardware).
>>>>
>>>> The symptoms are:
>>>> Receiving data is plenty fast (I can max out my internet connection
>>>> easily, and with iperf3 I get ~900Mbit/s).
>>>> Transmitting data from the device is unfortunately very slow,
>>>> traffic sometimes even stalls completely.
>>>>
>>>> I have attached the iperf results and the output of
>>>> /sys/kernel/debug/stmmaceth/eth0/descriptors_status.
>>>> Below you can find the ifconfig, netstat and stmmac dma_cap info
>>>> (*after* I ran all tests).
>>>>
>>>> The "involved parties" are:
>>>> - Meson GXBB specific network configuration registers (I have have
>>>> double-checked them with the reference drivers: everything seems
>>>> fine here)
>>>> - stmmac: it seems that nobody else has reported these kind of
>>>> issues so far, however I'd still like to hear where I should
>>>> enable some debugging bits to rule out any stmmac bug
>>>
>>>
>>> On my side, I just tested on the same "kind" of system:
>>> -SYNOPSYS GMAC 3.7
>>> -RTL8211EG as PHY
>>>
>>> With I perf, I reach:
>>> -RX: 932 Mbps
>>> -TX: 820Mbps
>>>
>>> Can you check ethtool -S eth0 (most precisely "MMC"counter and
>>> errors) ? Which kernel version do you use ?
>> I am using a 4.8.0-rc4 kernel, based on Kevin's "integration" branch:
>> [0] Unfortunately I don't have access to my device in the next few
>> days, but I'll keep you updated once I have the ethtool output.
>>
>>
>> Thanks for your time
>> Regards,
>> Martin
>>
>>
>> [0]
>> https://git.kernel.org/cgit/linux/kernel/git/khilman/linux-amlogic.git/log/?h=v4.8/integ
>>
>> _______________________________________________
>> linux-amlogic mailing list
>> linux-amlogic at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-amlogic
>>
>
next prev parent reply other threads:[~2016-09-26 6:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 20:39 Martin Blumenstingl
2016-09-12 16:37 ` Alexandre Torgue
2016-09-12 21:26 ` Martin Blumenstingl
2016-09-17 21:23 ` André Roth
2016-09-26 6:17 ` Giuseppe CAVALLARO [this message]
2016-10-01 15:58 ` Martin Blumenstingl
2016-11-03 16:36 ` Jerome Brunet
2016-11-05 12:20 ` Martin Blumenstingl
2016-11-13 19:20 ` André Roth
[not found] ` <216F2694-1C1D-44DA-AC15-57ED15C24BBE@bluematt.me>
2016-09-12 21:29 ` Martin Blumenstingl
2016-09-14 15:30 ` Giuseppe CAVALLARO
2016-09-18 20:42 ` André Roth
2016-09-19 5:38 ` Giuseppe CAVALLARO
2016-10-01 20:15 ` Martin Blumenstingl
2016-10-01 20:40 ` Martin Blumenstingl
2016-10-31 10:25 ` André Roth
2016-11-03 16:57 ` Jerome Brunet
2016-11-07 10:59 ` Giuseppe CAVALLARO
2016-11-07 17:37 ` Martin Blumenstingl
2016-11-14 7:47 ` Giuseppe CAVALLARO
2016-11-14 11:02 ` Jerome Brunet
2016-11-14 15:00 ` Andreas Färber
2016-11-15 11:27 ` Jerome Brunet
2016-11-13 19:13 ` André Roth
2016-11-14 10:49 ` Jerome Brunet
2016-11-17 18:44 ` André Roth
2016-11-17 21:47 ` Jerome Brunet
2016-10-01 20:26 ` Martin Blumenstingl
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=d59f6e2c-15ff-779d-da2f-8eb5f5a535a6@st.com \
--to=peppe.cavallaro@st.com \
--cc=linus-amlogic@lists.infradead.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
all inboxes | Powered by JetHome®