FS#3246 - ar8216.c and ar8327.c does not read incoming packets (RX packets and bytes always at 0) #8119
Labels
flyspray
kernel
pull request/issue with Linux kernel related changes
release/19.07
pull request/issue targeted (also) for OpenWrt 19.07 release
retiredtab:
Device is Dlink DIR615C1 running 19.07 doesn't respond to pings. Device has been reset to factory defaults, but doesn't respond to pings.
ifconfig shows no RX packets and no RX bytes on eth0 interface.
root@OpenWrt:/# ifconfig
br-lan Link encap:Ethernet HWaddr 00:22:B0:BA:50:1F
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:378 (378.0 B)
eth0 Link encap:Ethernet HWaddr 00:22:B0:BA:50:1F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1475 (1.4 KiB)
Interrupt:4
Same DIR615C1 running 18.06.08 works fine.
If I compile the current snapshot with the 18.06.8 code from ar8216.c, ar8216.h, ar8327.c and ar8327.h (the last two were required because of compilation errors), the snapshot image with the older 18.06.8 ar8216 drivers works fine.
There are significant changes in the way the ar8216 is initialized and setup from 18.06.8 to 19.07.1 and the latter code is not reading incoming packets because RX packets and RX bytes are always 0.
Code found in
target/linux/generic/files/drivers/net/phy
Details at
https://forum.openwrt.org/t/lan-doesnt-work-in-19-07-2-custom-build/61945/
The text was updated successfully, but these errors were encountered: