All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: lorenzo.bianconi@redhat.com, sean.wang@mediatek.com
Cc: nbd@nbd.name, jf@simonwunderlich.de,
	linux-wireless@vger.kernel.org,
	linux-mediatek@lists.infradead.org,
	Sean Wang <sean.wang@mediatek.com>
Subject: Re: mt76: MT7921K monitor mode not working
Date: Mon, 06 Dec 2021 14:05:29 +0100	[thread overview]
Message-ID: <12706913.cppxkphV4n@ripper> (raw)
In-Reply-To: <1638579304-17794-1-git-send-email-sean.wang@mediatek.com>


[-- Attachment #1.1: Type: text/plain, Size: 2051 bytes --]

On Saturday, 4 December 2021 01:55:04 CET sean.wang@mediatek.com wrote:
> >ack, I agree, but I guess the point here is what is the difference (from the fw pov) if you disable runtime-pm/deep-sleep before/after the vif is added. I guess it is supposed to be the same, right?
> 
> yes, it is supposed to be the same.

Two things which were noticed too:

First finding: If I run `iw dev mon0 del` after a non-working tcpdump dump 
session then I get following error messages before my complete system freezes:

    [  492.812050] mt7921e 0000:04:00.0: Message 40000002 (seq 14) timeout
    [  492.818587] mt7921e 0000:04:00.0: chip reset
    [  495.883934] mt7921e 0000:04:00.0: Message 00000046 (seq 15) timeout

Second one: We cannot see beacons on 2.4Ghz and 5GHz when runtime-pm + deep-
sleep is set to 0.



Regarding the initial problem: following works (when ignoring the missing 
beacons for now):

    echo 0 > /sys/kernel/debug/ieee80211/phy0/mt76/runtime-pm
    echo 0 > /sys/kernel/debug/ieee80211/phy0/mt76/deep-sleep
    iw dev wlp4s0 del
    iw phy0 interface add mon0 type monitor
    ip link set up dev mon0
    iw dev mon0 set channel 11
    tcpdump -ni mon0


What is often not working:

    iw dev wlp4s0 del
    iw phy0 interface add mon0 type monitor
    ip link set up dev mon0
    iw dev mon0 set channel 11
    tcpdump -ni mon0 &
    sleep 10
    echo 0 > /sys/kernel/debug/ieee80211/phy0/mt76/runtime-pm
    sleep 5
    echo 0 > /sys/kernel/debug/ieee80211/phy0/mt76/deep-sleep


What I have seem to break sometimes (but cannot reproduce reliably):

    iw dev wlp4s0 del
    iw phy0 interface add mon0 type monitor
    ip link set up dev mon0
    iw dev mon0 set channel 11
    echo 0 > /sys/kernel/debug/ieee80211/phy0/mt76/runtime-pm
    echo 0 > /sys/kernel/debug/ieee80211/phy0/mt76/deep-sleep
    tcpdump -ni mon0


The channel 11 is rather busy. It is for example also used for our community 
mesh network in the city center - so is rather easy for me to see that it is 
able to sniff traffic or not.

Kind regards,
	Sven

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven@narfation.org>
To: lorenzo.bianconi@redhat.com, sean.wang@mediatek.com
Cc: nbd@nbd.name, jf@simonwunderlich.de,
	linux-wireless@vger.kernel.org,
	linux-mediatek@lists.infradead.org,
	Sean Wang <sean.wang@mediatek.com>
Subject: Re: mt76: MT7921K monitor mode not working
Date: Mon, 06 Dec 2021 14:05:29 +0100	[thread overview]
Message-ID: <12706913.cppxkphV4n@ripper> (raw)
In-Reply-To: <1638579304-17794-1-git-send-email-sean.wang@mediatek.com>

[-- Attachment #1: Type: text/plain, Size: 2051 bytes --]

On Saturday, 4 December 2021 01:55:04 CET sean.wang@mediatek.com wrote:
> >ack, I agree, but I guess the point here is what is the difference (from the fw pov) if you disable runtime-pm/deep-sleep before/after the vif is added. I guess it is supposed to be the same, right?
> 
> yes, it is supposed to be the same.

Two things which were noticed too:

First finding: If I run `iw dev mon0 del` after a non-working tcpdump dump 
session then I get following error messages before my complete system freezes:

    [  492.812050] mt7921e 0000:04:00.0: Message 40000002 (seq 14) timeout
    [  492.818587] mt7921e 0000:04:00.0: chip reset
    [  495.883934] mt7921e 0000:04:00.0: Message 00000046 (seq 15) timeout

Second one: We cannot see beacons on 2.4Ghz and 5GHz when runtime-pm + deep-
sleep is set to 0.



Regarding the initial problem: following works (when ignoring the missing 
beacons for now):

    echo 0 > /sys/kernel/debug/ieee80211/phy0/mt76/runtime-pm
    echo 0 > /sys/kernel/debug/ieee80211/phy0/mt76/deep-sleep
    iw dev wlp4s0 del
    iw phy0 interface add mon0 type monitor
    ip link set up dev mon0
    iw dev mon0 set channel 11
    tcpdump -ni mon0


What is often not working:

    iw dev wlp4s0 del
    iw phy0 interface add mon0 type monitor
    ip link set up dev mon0
    iw dev mon0 set channel 11
    tcpdump -ni mon0 &
    sleep 10
    echo 0 > /sys/kernel/debug/ieee80211/phy0/mt76/runtime-pm
    sleep 5
    echo 0 > /sys/kernel/debug/ieee80211/phy0/mt76/deep-sleep


What I have seem to break sometimes (but cannot reproduce reliably):

    iw dev wlp4s0 del
    iw phy0 interface add mon0 type monitor
    ip link set up dev mon0
    iw dev mon0 set channel 11
    echo 0 > /sys/kernel/debug/ieee80211/phy0/mt76/runtime-pm
    echo 0 > /sys/kernel/debug/ieee80211/phy0/mt76/deep-sleep
    tcpdump -ni mon0


The channel 11 is rather busy. It is for example also used for our community 
mesh network in the city center - so is rather easy for me to see that it is 
able to sniff traffic or not.

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-12-06 13:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <YapTmM3EztojTS9F@lore-desk--annotate>
2021-12-04  0:55 ` mt76: MT7921K monitor mode not working sean.wang
2021-12-04  0:55   ` sean.wang
2021-12-06 13:05   ` Sven Eckelmann [this message]
2021-12-06 13:05     ` Sven Eckelmann
2021-12-16 21:13     ` Lorenzo Bianconi
2021-12-16 21:13       ` Lorenzo Bianconi
2021-12-17  7:38       ` Sven Eckelmann
2021-12-17  7:38         ` Sven Eckelmann
2022-01-11 10:53       ` Sven Eckelmann
2022-01-11 10:53         ` Sven Eckelmann
2022-01-11 11:02         ` Lorenzo Bianconi
2022-01-11 11:02           ` Lorenzo Bianconi
     [not found] <YapBMGjLcjuBo/vw@lore-desk--annotate>
2021-12-03 17:10 ` sean.wang
2021-12-03 17:10   ` sean.wang
2021-12-03 17:27   ` Lorenzo Bianconi
2021-12-03 17:27     ` Lorenzo Bianconi
2021-12-01  9:41 Jan Fuchs
2021-12-01  9:41 ` Jan Fuchs
2021-12-02 22:13 ` Lorenzo Bianconi
2021-12-02 22:13   ` Lorenzo Bianconi
2021-12-03 15:32   ` Sven Eckelmann
2021-12-03 15:32     ` Sven Eckelmann
2021-12-03 16:09     ` Lorenzo Bianconi
2021-12-03 16:09       ` Lorenzo Bianconi

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=12706913.cppxkphV4n@ripper \
    --to=sven@narfation.org \
    --cc=jf@simonwunderlich.de \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=nbd@nbd.name \
    --cc=sean.wang@mediatek.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.