linux-amlogic.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: neolynx@gmail.com (André Roth)
To: linus-amlogic@lists.infradead.org
Subject: stmmac/RTL8211F/Meson GXBB: TX throughput problems
Date: Mon, 31 Oct 2016 11:25:24 +0100	[thread overview]
Message-ID: <20161031112524.4c4ee8f8@gmail.com> (raw)
In-Reply-To: <CAFBinCC0HiEXx5mELztH6jYfUq2f1u0Tb+pSzAvwQSu9vYydGQ@mail.gmail.com>


Hi all,
 
> on my device this results in:
> [0xc9410018] = 0x2000000
> [0xc9410030] = 0x0
> [0xc941003c] = 0x0
> [0xc9411000] = 0x1100802
> [0xc9411018] = 0x2202006
> [0xc9411028] = 0x0
> 
> maybe someone else could try the command from above on his device
> (running the original Amlogic kernel).

those registers have the same value on an original image from
hardkernel: 

Linux odroid64 3.14.65-65 #1 SMP PREEMPT Sat May 28
02:50:51 BRT 2016 aarch64 aarch64 aarch64 GNU/Linux

> please also state if ethernet is working properly on the original
> kernel (and preferably which device/board this is).

yes, the ethernet works flawless in 100 and 1000 Mbit/s on the 3.14
kernel.

I can now confirm that both 100 and 1000 Mbit/s do not work properly
on the 4.8/integ branch. the network connection is interrupted after
some outbound traffic. it can be recovered by running a ifdown/ifup
which restarts dhclient, which I think is able to somehow reset the
interface. 

Anything I can help to debug the issue further ?

Regards,

 Andr?
 

  parent reply	other threads:[~2016-10-31 10:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-11 20:39 stmmac/RTL8211F/Meson GXBB: TX throughput problems 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
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 [this message]
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=20161031112524.4c4ee8f8@gmail.com \
    --to=neolynx@gmail.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;
as well as URLs for NNTP newsgroup(s).