wifi network freeze Intermittently
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
The ping lost or time increase Intermittently
This issue cause network freeze
This happens in mt7603(2.4G) or mt7612e(5G) on mt7621
ping log:
PING 192.168.16.1 (192.168.16.1) 56(84) bytes of data.
64 bytes from 192.168.16.1: icmp_seq=1 ttl=64 time=4.37 ms
64 bytes from 192.168.16.1: icmp_seq=2 ttl=64 time=1.18 ms
64 bytes from 192.168.16.1: icmp_seq=3 ttl=64 time=1.24 ms
64 bytes from 192.168.16.1: icmp_seq=4 ttl=64 time=2.70 ms
64 bytes from 192.168.16.1: icmp_seq=5 ttl=64 time=1.17 ms
64 bytes from 192.168.16.1: icmp_seq=6 ttl=64 time=1.20 ms
64 bytes from 192.168.16.1: icmp_seq=7 ttl=64 time=2.11 ms
64 bytes from 192.168.16.1: icmp_seq=8 ttl=64 time=1.15 ms
64 bytes from 192.168.16.1: icmp_seq=9 ttl=64 time=18.0 ms
64 bytes from 192.168.16.1: icmp_seq=10 ttl=64 time=1.25 ms
64 bytes from 192.168.16.1: icmp_seq=11 ttl=64 time=2.78 ms
64 bytes from 192.168.16.1: icmp_seq=12 ttl=64 time=2.30 ms
64 bytes from 192.168.16.1: icmp_seq=13 ttl=64 time=2.24 ms
64 bytes from 192.168.16.1: icmp_seq=14 ttl=64 time=2.61 ms
64 bytes from 192.168.16.1: icmp_seq=15 ttl=64 time=224 ms
64 bytes from 192.168.16.1: icmp_seq=16 ttl=64 time=208 ms
64 bytes from 192.168.16.1: icmp_seq=17 ttl=64 time=2.31 ms
64 bytes from 192.168.16.1: icmp_seq=18 ttl=64 time=2.45 ms
64 bytes from 192.168.16.1: icmp_seq=19 ttl=64 time=1.15 ms
64 bytes from 192.168.16.1: icmp_seq=20 ttl=64 time=2.67 ms
64 bytes from 192.168.16.1: icmp_seq=21 ttl=64 time=2.71 ms
64 bytes from 192.168.16.1: icmp_seq=22 ttl=64 time=0.973 ms
64 bytes from 192.168.16.1: icmp_seq=23 ttl=64 time=1.07 ms
64 bytes from 192.168.16.1: icmp_seq=24 ttl=64 time=2.75 ms
64 bytes from 192.168.16.1: icmp_seq=25 ttl=64 time=4.18 ms
64 bytes from 192.168.16.1: icmp_seq=26 ttl=64 time=3.37 ms
64 bytes from 192.168.16.1: icmp_seq=27 ttl=64 time=2.64 ms
64 bytes from 192.168.16.1: icmp_seq=28 ttl=64 time=2.51 ms
64 bytes from 192.168.16.1: icmp_seq=29 ttl=64 time=2.61 ms
64 bytes from 192.168.16.1: icmp_seq=30 ttl=64 time=2.70 ms
64 bytes from 192.168.16.1: icmp_seq=31 ttl=64 time=1.17 ms
64 bytes from 192.168.16.1: icmp_seq=32 ttl=64 time=218 ms
64 bytes from 192.168.16.1: icmp_seq=33 ttl=64 time=96.1 ms
64 bytes from 192.168.16.1: icmp_seq=34 ttl=64 time=79.5 ms
64 bytes from 192.168.16.1: icmp_seq=35 ttl=64 time=1.22 ms
64 bytes from 192.168.16.1: icmp_seq=36 ttl=64 time=2.70 ms
64 bytes from 192.168.16.1: icmp_seq=37 ttl=64 time=1.15 ms
64 bytes from 192.168.16.1: icmp_seq=38 ttl=64 time=2.45 ms
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the intermittent ping latency on the reported mt7603 and mt7612e hardware running on mt7621, using the supplied ping pattern. Then inspect the relevant mt76 driver code and collect the missing environment, logs, and reproduction details. Done means identifying a reproducible driver fault and confirming a fix removes the packet loss or latency spikes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100