freifunk-franken
/
firmware
9
7
Fork 13
Code Issues 48 Pull Requests 7 Releases 17 Wiki Activity

Frequent WAN disconnects on ath79 platform #61

New Issue
Closed
opened 2021-01-05 14:01:55 +01:00 by mantis-bot · 1 comment
mantis-bot commented 2021-01-05 14:01:55 +01:00
Copy Link

The ar8216 switch driver has a problem that leads to occational (and sometimes frequent) WAN dis- and reconnects as well as link speed drops.
This only occurs with a subset of devices from ath79 target, ar71xx (i.e. last released stable firmware) is fine:

[18580.106696] eth0: link up (100Mbps/Full duplex)
[19014.825937] eth0: link up (10Mbps/Half duplex)
[19055.384105] eth0: link up (100Mbps/Full duplex)
[21927.853366] eth0: link up (10Mbps/Half duplex)
[22003.771999] eth0: link up (100Mbps/Full duplex)
[23743.685216] eth0: link down
[23744.723679] eth0: link up (100Mbps/Full duplex)
[23756.242265] eth0: link down
[23757.283590] eth0: link up (100Mbps/Full duplex)
[24075.522397] eth0: link up (10Mbps/Half duplex)
[24090.081802] eth0: link up (100Mbps/Full duplex)
[24100.481809] eth0: link up (10Mbps/Half duplex)
[24166.001178] eth0: link up (100Mbps/Full duplex)
[24500.880989] eth0: link up (10Mbps/Half duplex)

In production, this may lead to an installation becoming inaccessible for days.

Further information: https://bugs.openwrt.org/index.php?do=details&task_id=2216

The problem has recently been "fixed" in OpenWrt master: 86fdc8abed

I have cherry-picked this into 19.07 and just sent a patch to the franken-dev list.

Reported by: Adrian Schmutzler
Submitted on: 2020-09-30
Imported from: https://mantis.freifunk-franken.de/view.php?id=0000145

The ar8216 switch driver has a problem that leads to occational (and sometimes frequent) WAN dis- and reconnects as well as link speed drops. This only occurs with a subset of devices from ath79 target, ar71xx (i.e. last released stable firmware) is fine: [18580.106696] eth0: link up (100Mbps/Full duplex) [19014.825937] eth0: link up (10Mbps/Half duplex) [19055.384105] eth0: link up (100Mbps/Full duplex) [21927.853366] eth0: link up (10Mbps/Half duplex) [22003.771999] eth0: link up (100Mbps/Full duplex) [23743.685216] eth0: link down [23744.723679] eth0: link up (100Mbps/Full duplex) [23756.242265] eth0: link down [23757.283590] eth0: link up (100Mbps/Full duplex) [24075.522397] eth0: link up (10Mbps/Half duplex) [24090.081802] eth0: link up (100Mbps/Full duplex) [24100.481809] eth0: link up (10Mbps/Half duplex) [24166.001178] eth0: link up (100Mbps/Full duplex) [24500.880989] eth0: link up (10Mbps/Half duplex) In production, this may lead to an installation becoming inaccessible for days. Further information: https://bugs.openwrt.org/index.php?do=details&task_id=2216 The problem has recently been "fixed" in OpenWrt master: https://github.com/openwrt/openwrt/commit/86fdc8abed5992a74078b000b5ff9da723b6f46b I have cherry-picked this into 19.07 and just sent a patch to the franken-dev list. Reported by: Adrian Schmutzler Submitted on: 2020-09-30 Imported from: https://mantis.freifunk-franken.de/view.php?id=0000145
adschm was assigned by mantis-bot 2021-01-05 14:01:55 +01:00
fbl added the
mantis
 label 2021-01-05 14:24:07 +01:00
fbl added this to the 20210211-beta milestone 2021-01-05 15:51:11 +01:00
fbl added the
upstream
 label 2021-01-05 15:51:35 +01:00
adschm commented 2021-01-05 16:31:46 +01:00
Owner
Copy Link

This has been fixed with OpenWrt 19.07.5.

This has been fixed with OpenWrt 19.07.5.
adschm added the
fixed
 label 2021-01-05 16:35:17 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
0.5.x
20240401
20240401-beta
20240119-beta
20230330
20230321-beta
20160213-beta
20221201
20221019
20220814
20220413
20220405-beta
20211224
20211220
20211201-beta
20210226
20210218
20210211-beta
20200501
20200423-beta
20200118
20191224
20191214-beta
20191130-alpha
20191123-alpha
20181202
20181128-beta
20180802
20180802-beta
20180726-beta
20180304-alpha
20180303-alpha
20170918
20170918-beta
20170218-alpha
20170110
20170110-beta
20161105-beta
20161008-beta
20160506
20160506-beta
20160310
0.5.2
0.5.2-b2
0.5.2-b1
0.5.1
0.5.1-b2
0.5.1-b1
0.5.0
0.5.0-b1
0.4.3
0.4.2
0.4.1
0.4.0ol
0.4.0f
0.4.0rc5f
0.4.0rc4ol
0.4.0rc4f
0.4.0rc3f
0.4.0rc2f
0.3.999f
0.3.999
0.3.998
0.3.99
0.3
0.2.1
0.2
0.1
Labels
Clear labels   
RFC

   
RFT

   
WIP

   
blocked

   
bsp

touching bsp files or adding devices

  
bug

Something is not working

  
build/scripts/tools

touching buildscript or other tools

  
duplicate

This issue or pull request already exists

  
feature

New feature

  
fixed

Issue that got resolved

  
layer3

only for layer3 FW

  
mantis

Imported from mantis

  
more details required

Reported information is insufficient to debug the issue

  
needs changes

   
node

only for node FW

  
packages/fff

touching our packages

  
rejected

Rejected or won't fix

  
security

   
trivial

simple non-functional changes that are mostly matter of taste

  
upstream

touching upstream version, build or feed patches

No Label
RFC
RFT
WIP
blocked
bsp
bug
build/scripts/tools
duplicate
feature
fixed
layer3
mantis
more details required
needs changes
node
packages/fff
rejected
security
trivial
upstream
Milestone
Clear milestone
No items
No Milestone
20210211-beta
Assignees
Clear assignees
No Assignees
adschm
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: freifunk-franken/firmware#61
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?