Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1694669
| From | Neil Armstrong <narmstrong@baylibre.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] ARM64: meson-gxl: disable broken eee |
| Date | 2017-07-24 14:10 +0200 |
| Message-ID | <u6Kls-4C2-21@gated-at.bofh.it> (permalink) |
| References | <u0qpr-54Y-3@gated-at.bofh.it> <u64vT-3BB-3@gated-at.bofh.it> <u6syd-1RK-5@gated-at.bofh.it> |
| Organization | Baylibre |
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@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
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH] ARM64: meson-gxl: disable broken eee Kevin Hilman <khilman@baylibre.com> - 2017-07-22 17:30 +0200
Re: [PATCH] ARM64: meson-gxl: disable broken eee Joseph Kogut <joseph.kogut@gmail.com> - 2017-07-23 19:10 +0200
Re: [PATCH] ARM64: meson-gxl: disable broken eee Neil Armstrong <narmstrong@baylibre.com> - 2017-07-24 14:10 +0200
Re: [PATCH] ARM64: meson-gxl: disable broken eee Neil Armstrong <narmstrong@baylibre.com> - 2017-07-24 14:30 +0200
Re: [PATCH] ARM64: meson-gxl: disable broken eee Jerome Brunet <jbrunet@baylibre.com> - 2017-07-24 18:10 +0200
Re: [PATCH] ARM64: meson-gxl: disable broken eee Martin Blumenstingl <martin.blumenstingl@googlemail.com> - 2017-07-24 20:30 +0200
Re: [PATCH] ARM64: meson-gxl: disable broken eee Jerome Brunet <jbrunet@baylibre.com> - 2017-07-24 20:40 +0200
Re: [PATCH] ARM64: meson-gxl: disable broken eee crow <crow@linux.org.ba> - 2017-07-25 19:10 +0200
csiph-web