From: Oleksiy Protas <elfy.ua@gmail.com>
To: elfy.ua@gmail.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: MikroTik R11e 5HnD monitor mode
Date: Wed, 14 May 2025 22:11:35 +0300 [thread overview]
Message-ID: <20250514191135.375855-1-elfy.ua@gmail.com> (raw)
In-Reply-To: <20250514180413.373876-1-elfy@ecognize.me>
Additional findings so far for the RX side of the problem:
1. Upon coming from a modprobe && iw set monitor && ifconfig the interface receives nothing.
2. The inferface starts hearing packets after coming of a reset (verifiable with debugfs).
Changing frequencies isn't required, just resetting the interface allows to grab a portion of traffic.
3. Judging by tcpdump timestamps, around 1.4 ms worth of traffic is collected before going silent again.
4. After a reset we have a 2.5 ms gap between these entries (full debugging):
>[23363.517582] ath: phy14: TS Start 0xc4268000 End 0xc426c800 Virt 00000000973829f0, Size 512
>[23363.520142] ath: phy14: Doing Tx IQ Cal for chain 0
5. Then the calibration goes on for some time and ends like this after ~1ms:
>[23363.520886] ath: phy14: rx chain 1: mag corr=-13 phase corr=0
>[23363.520891] ath: phy14: rx chain 1: iq corr coeff=fffff980
>[23363.520928] ath: phy14: starting IQ Mismatch Calibration
6. Last messages before the log goes silent until the next reset:
>[23363.521178] ath: phy14: New interrupt mask 0xf0000473
>[23363.521182] ath: phy14: new IMR 0x81800175
>[23363.521187] ath: phy14: enable IER
>[23363.521195] ath: phy14: AR_IMR 0x81800175 IER 0x1
7. If I apply the patch above, the ANI calibration timer keeps going past this point, but nothing else is.
prev parent reply other threads:[~2025-05-14 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 16:19 MikroTik R11e 5HnD monitor mode Oleksiy Protas
2025-05-14 18:04 ` [PATCH] " Oleksiy Protas
2025-05-14 18:04 ` [PATCH] ath9k: keep ANI in " Oleksiy Protas
2025-08-11 12:18 ` Toke Høiland-Jørgensen
2025-05-14 19:11 ` Oleksiy Protas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250514191135.375855-1-elfy.ua@gmail.com \
--to=elfy.ua@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).