Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [PATCH 5/5] mt76: enable Airtime Queue Limit support
To:     =?UTF-8?Q?Toke_H=c3=b8iland-J=c3=b8rgensen?= <toke@redhat.com>,
        Felix Fietkau <nbd@nbd.name>, linux-wireless@vger.kernel.org
References: <20200127181754.2810-1-nbd@nbd.name>
 <20200127181754.2810-5-nbd@nbd.name> <875zgqfoqu.fsf@toke.dk>
 <aca37dcb-c76d-d239-0d0e-61b73afc5d8f@dd-wrt.com> <87lfoyw71d.fsf@toke.dk>
From:   Sebastian Gottschall <s.gottschall@dd-wrt.com>
Message-ID: <02e9c960-44ba-c879-be65-d9a9a840543d@dd-wrt.com>
Date:   Thu, 20 Feb 2020 18:20:44 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101
 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <87lfoyw71d.fsf@toke.dk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

the interface is bridged to a bridge named br0 and owns the local lan ip.
its a typical setup. lan switch is bridged together with ap interface
iperf was not running on the device itself needs to be mentioned. i was 
running iperf -s on a device which was  connected by ethernet to this 
device.
my client was a simple lenovo p52 laptop with a iwlwifi 9560 card wich 
was using iperf -c x.x.x.x -P 32 -i 1

Am 19.02.2020 um 23:23 schrieb Toke Høiland-Jørgensen:
> Sebastian Gottschall <s.gottschall@dd-wrt.com> writes:
>
>> nope (iperf3 with 32 parallel streams after 5 seconds of running)
>>
>> STA 30:24:32????f9:c4 AC 2 txq pending airtime underflow: 4294967208, 88
>> Modules linked in: fast_classifier mt7615e mt76 mac80211 compat
>> CPU: 3 PID: 1890 Comm: hostapd Not tainted 4.14.171 #187
>> Stack : 00000000 00000001 00000040 8007e454 80490000 8048bc8c 80610000
>> 805aee78
>>           8058850c 8770b864 870f289c 805f07a7 80582204 00000001 8770b808
>> 805f60a8
>>           00000000 00000000 80650000 00000000 81147bb8 0000011e 00000007
>> 00000000
>>           00000000 80660000 80660000 68203a6d 80000000 80610000 00000000
>> 873079ec
>>           873a4654 00000775 00000000 00000001 00000000 80230b88 0000000c
>> 8065000c
>>           ...
>> Call Trace:
>> [<800153a0>] show_stack+0x58/0x100
>> [<80438c54>] dump_stack+0xa4/0xe0
>> [<80035050>] __warn+0xe4/0x144
>> [<80034c8c>] warn_slowpath_fmt+0x30/0x3c
>> [<873079ec>] _616+0x110/0x214 [mac80211]
>> [<87301ce0>] _535+0x15c/0x4f8 [mac80211]
>> [<804224f0>] br_handle_frame_finish+0x4e0/0x524
>> [<873d5160>] _49+0x50/0xa4 [mt76]
>> [<87606e30>] _61+0x1e8/0x224 [mt7615e]
> Huh, why is there a bridge function name in there in the middle of the
> callstack?
>
> -Toke
>
>