mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] ARM64: meson-gxl: disable broken eee
Date: Mon, 24 Jul 2017 14:06:04 +0200	[thread overview]
Message-ID: <cf71b3c2-29d7-3bdb-0d00-872f5e1267e2@baylibre.com> (raw)
In-Reply-To: <CAMWSM7hB1e8gJEY3RvQ6UyWsZC0qB-rV2PTxun_4mdzO0e8X-A@mail.gmail.com>

On 07/23/2017 07:03 PM, Joseph Kogut wrote:
> Hi Kevin,
> 
> I tested on a P212 reference board, which is currently the only GXL
> based board I have.
> 
> Before applying the patch, high activity on the ethernet interface
> would cause the link to break, requiring the interface to be brought
> down and back up before it would work again. After applying the patch,
> I could not get the link to break with any transfers.
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

Hi Joseph,

[please keep the history of the conversation when replying]

Is it a original P212 board, or a board based on the P212 ref design ?

I'm currently testing the v4.13-rc2 on the official P212 board we received from Amlogic
and using iperf3 in both directions, I have an issue after a few minutes running iperf3 with :

# while true ; do iperf3 -c 192.168.1.21 ; iperf3 -c 192.168.1.21 -R ; done

That cycles between the two iperf directions.

After a few minutes, it stalls with :

Connecting to host 192.168.1.21, port 5201
[  4] local 192.168.1.183 port 51286 connected to 192.168.1.21 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec  1.64 MBytes  13.7 Mbits/sec    2   1.41 KBytes
[  4]   1.00-2.00   sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes
[  4]   2.00-3.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes
[  4]   3.00-4.00   sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes
[  4]   4.00-5.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes
[  4]   5.00-6.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes
[  4]   6.00-7.00   sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes
[  4]   7.00-8.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes
[  4]   8.00-9.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes


And then, after:
# ifconfig eth0 down
# ifconfig eth0 up

It cycles between :
[ 1483.009919] meson8b-dwmac c9410000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 1487.105725] meson8b-dwmac c9410000.ethernet eth0: Link is Down
[ 1490.177943] meson8b-dwmac c9410000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 1494.273713] meson8b-dwmac c9410000.ethernet eth0: Link is Down

and so on.

And this patch does not fix this at all.

It seems to be more a PHY driver issue here.

Could you share the results with the same command ?

Neil

  reply	other threads:[~2017-07-24 12:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-07  1:32 Joseph Kogut
2017-07-22 15:26 ` Kevin Hilman
2017-07-23 17:03   ` Joseph Kogut
2017-07-24 12:06     ` Neil Armstrong [this message]
2017-07-24 12:26       ` Neil Armstrong
2017-07-24 16:09         ` Jerome Brunet
2017-07-24 18:20           ` Martin Blumenstingl
2017-07-24 18:32             ` Jerome Brunet
2017-07-25 17:03               ` crow

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=cf71b3c2-29d7-3bdb-0d00-872f5e1267e2@baylibre.com \
    --to=narmstrong@baylibre.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®