On Thu, Oct 17, 2019 at 11:03 PM Rudolf Spring wrote:
>
> Can you reproduce the error in the lab ? Same behaviour with Kernel 5.3.6.
>
Yes. We are trying to reproduce in our local lab. We will update once
we have reproduction.
>
> eth0: flags=4163 mtu 9000
> ether a8:20:66:28:e6:95 txqu
Can you reproduce the error in the lab ? Same behaviour with Kernel 5.3.6.
eth0: flags=4163 mtu 9000
ether a8:20:66:28:e6:95 txqueuelen 1000 (Ethernet)
RX packets 13844854 bytes 2298858755 (2.1 GiB)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 14831625
With Kernel 5.3.2. Interesting all are tx_mac_errors.
ifconfig eth0
eth0: flags=4163 mtu 9000
ether a8:20:66:28:e6:95 txqueuelen 1000 (Ethernet)
RX packets 1649204 bytes 775261068 (739.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1144621 bytes
The output of dmesg and ethtool is identical between 4.19.72 and 5.3.2. Any
suggestions ?
:01:00.0: enabling device ( -> 0002)
[1.140738] tg3 :01:00.0 eth0: Tigon3 [partno(BCM957766a) rev 57766001]
(PCI Express) MAC address a8:20:66:28:e6:95
[1.140741] tg3 :01:00.0 eth0:
On Tue, Oct 1, 2019 at 7:31 AM Rudolf Spring wrote:
>
> Hello - Since Kernel Version 5.0 (5.0.x/5.1.x/5.2.x and now 5.3.x) my
> BCM57765 refuses to work correctly. The same system configuration works
> without problems on the latest stable Gentoo 4.19.72 Kernel. So the changes
> from 4.19 to 5.
Hello - Since Kernel Version 5.0 (5.0.x/5.1.x/5.2.x and now 5.3.x) my BCM57765
refuses to work correctly. The same system configuration works without problems
on the latest stable Gentoo 4.19.72 Kernel. So the changes from 4.19 to 5.0
include some code that is responsible for the hick-up. The pr
