On 02/28/2017 01:41 PM, Jens Axboe wrote:
> On 02/28/2017 11:02 AM, Jens Axboe wrote:
>> Hi,
>>
>> I'm hitting this one a lot with current -git, which is this one:
>>
>> if (iwl_mvm_is_dqa_supported(mvm)) {
>> iwl_mvm_disable_sta_queues(mvm, vif, mvm_sta);
>> /*
>> * If pending_frames is set at this point - it must be
>> * driver internal logic error, since queues are empty
>> * and removed successuly.
>> * warn on it but set it to 0 anyway to avoid station
>> * not being removed later in the function
>> */
>> WARN_ON(atomic_xchg(&mvm->pending_frames[sta_id], 0));
>> }
>>
>> It's hit 4 times over the last day. The bug is probably older than the
>> commit that added this warning:
>>
>> commit 94c3e614df2117626fccfac8f821c66e30556384
>> Author: Sara Sharon <sara.sharon@xxxxxxxxx>
>> Date: Wed Dec 7 15:04:37 2016 +0200
>>
>> iwlwifi: mvm: fix pending frame counter calculation
>>
>> but the pestering is new.
>
> Forgot to include the traces, find them below.
Not that folks have been jumping all over this, but in case someone is
curious, it triggered twice here today. For those two times, the value
of mvm->pending_frames[sta_id] was 80 and 39, respectively.
--
Jens Axboe
