mt7925e crashes occasionally in AP mode
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
in ap mode mt7925e crashes occasionally.
and there is not much output from dmesg.
i tried to disable ASPM, fastboot but result is same.
trying older and newer fw's did not changed situtations.
when crash occurs i get some output like that from dmesg:
[ 14.010930] mt7925e 0000:01:00.0: enabling device (0000 -> 0002)
[ 14.011227] mt7925e 0000:01:00.0: disabling ASPM L0s L1
[ 14.020518] mt7925e 0000:01:00.0: ASIC revision: 79250000
[ 14.106534] mt7925e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20231227093012a
[ 14.445882] mt7925e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20231227093232
[ 17.414227] mt7925e 0000:01:00.0 wlan0: entered allmulticast mode
[ 17.414415] mt7925e 0000:01:00.0 wlan0: entered promiscuous mode
[40042.476822] mt7925e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20231227093012a
[40042.818661] mt7925e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20231227093232
lspci output for this card:
lspci.txt
time to time i see also a timeout error like but not always:
mt7925e 0000:04:00.0: Message 00020003 (seq 15) timeout
interesting thing is that when it crashed i saw always on 'iw dev' normal but in reality card crashed and ssid lost.
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 reviewing lspci.txt and the supplied dmesg output, then reproduce the crash in AP mode while monitoring dmesg and checking iw dev. Compare cases with and without the intermittent Message 00020003 timeout. Done means identifying the mt7925e failure cause and preventing the AP interface from losing its SSID.
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
- 32/100