Skip to content

Commit ee2f5ae

Browse files
committed
target: install naywatch on mediatek targets
On 24.10 and 25.12 we sometimes see some kind of networking lockup on various mediatek devices. The device is just not reachable anymore and needs a reboot. The symptoms are similar to the ipq40xx ethernet lockup a few years ago, although the underlying cause is probably a different one, as ipq40xx is Qualcomm and we're looking at Mediatek here. Let's do the same workaround: naywatch, which reboots if ethernet neighbors disappear.
1 parent 5998255 commit ee2f5ae

File tree

3 files changed

+12
-0
lines changed

3 files changed

+12
-0
lines changed

group_vars/target_mediatek_filogic

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,7 @@
11
---
22

33
multicore: true
4+
5+
target__packages__to_merge:
6+
# Workaround for apparant mt7530 lockup
7+
- naywatch

group_vars/target_mediatek_mt7622

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,7 @@
11
---
22

33
multicore: true
4+
5+
target__packages__to_merge:
6+
# Workaround for apparant mt7530 lockup
7+
- naywatch

group_vars/target_ramips_mt7621

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,7 @@
11
---
22

33
multicore: true
4+
5+
target__packages__to_merge:
6+
# Workaround for apparant mt7530 lockup
7+
- naywatch

0 commit comments

Comments
 (0)