Description of problem: When connected to GBit network the performance of network is very low, and a lot of dropped packets. About 90 percent drop with a ping. Version-Release number of selected component (if applicable): 4.14.8 kernel How reproducible: It seems to be a known problem with different ethernet controllers on the board. Steps to Reproduce: 1. Get a board with problematic controller 2. Connect it to 1 GBit switch. (I use HP procurve) 3. Do a ping and check the packet drops. Actual results: Lot of packet losts on host on the same switch. Expected results: No lost packaets. Additional info: This thread on u-boot list cover the problem and how to see if the chip is right or "wrong". https://www.mail-archive.com/u-boot@lists.denx.de/msg207006.html I have checked the src rpm and the suggested patches seems not to there. There is no component for u-boot so I picked kernel but I think it might be u-boot.
The network performance is so bad that is very hard to get a update though. As a workaround for that is to use 100 Mbit/s switch.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.15.3-300.f27. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
I have tested with 4.15.3-300.f27 and 4.15.6-300.f27 and there is still not working.(In reply to Laura Abbott from comment #2) > We apologize for the inconvenience. There is a large number of bugs to go > through and several of them have gone stale. As kernel maintainers, we try > to keep up with bugzilla but due the rate at which the upstream kernel > project moves, bugs may be fixed without any indication to us. Due to this, > we are doing a mass bug update across all of the Fedora 27 kernel bugs. > > Fedora 27 has now been rebased to 4.15.3-300.f27. Please test this kernel > update (or newer) and let us know if you issue has been resolved or if it is > still present with the newer kernel. > > If you experience different issues, please open a new bug report for those. I have tested with 4.15.3-300.f27 and 4.15.6-300.f27 and there is still not working.
IIRC this indeed requires a fixup in u-boot, but that should be long in place... Anyways updating the component to uboot which is called uboot-tools for historical reasons, so that the right people see this.
Sounds very similar to the issues seen on the Pine64 [1]. Can you do a "dmesg | grep RTL" and add the details here, in theory should be a single line. [1] https://lists.denx.de/pipermail/u-boot/2018-February/320520.html
(In reply to Peter Robinson from comment #5) > Sounds very similar to the issues seen on the Pine64 [1]. Can you do a > "dmesg | grep RTL" and add the details here, in theory should be a single > line. > > [1] https://lists.denx.de/pipermail/u-boot/2018-February/320520.html Sure: [ 9.790610] RTL8211E Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=POLL) [ 9.803278] RTL8211E Gigabit Ethernet stmmac-0:01: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:01, irq=POLL) [ 150.631176] RTL8211E Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=POLL) This is with the ethertool setting that force it to 100mbit/s.
Can you give this u-boot a try and see if it fixes it for me? https://pbrobinson.fedorapeople.org/lime2/u-boot-sunxi-with-spl.bin
(In reply to Peter Robinson from comment #7) > Can you give this u-boot a try and see if it fixes it for me? > > https://pbrobinson.fedorapeople.org/lime2/u-boot-sunxi-with-spl.bin Where do you want this to be applied? Can I apply it on a running system?
Yes, you can apply to a running system but you need to reboot for the change to take effect. sudo dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 bs=1024 seek=8; sync;
(In reply to Peter Robinson from comment #9) > Yes, you can apply to a running system but you need to reboot for the change > to take effect. > > sudo dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 bs=1024 seek=8; sync; It did not solve the issue. 109 packets transmitted, 41 received, 62% packet loss, time 108043ms rtt min/avg/max/mdev = 0.436/0.989/1.231/0.256 ms
There may be more needed than just adding the config option in u-boot, it certainly solved the same issue with the same gig PHY on the Pine64 boards, but I'm not a low level eth PHY expert here.
Can you reset this on a newer Fedora/U-Boot
It is still not working on F28. (Updateded from F27)
Might be a problem similar to this: https://patchwork.kernel.org/patch/10515589/
According to the hardware release notes for that board, https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-OLinuXino-LIME2/hardware_revision_changes_log.txt , they have changed the Ethernet PHY a few times, and several parts of the power supply. Which revision of the board do you have?
The board has (c) 2017 Rev .G2 printed.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.