Open
Conversation
Contributor
|
Have you seen that naywatch "fixes" the problem? Otherwise lgtm |
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.
FFHener
force-pushed
the
mediatek-naywatch
branch
from
ee2f5ae to
a8aec5f
Compare
Contributor
Author
Nope, no idea :-) But it should. Maybe I can simulate the issue with |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.