Received-SPF: pass (google.com: domain of linux-wireless+bounces-6150-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Message-ID: <347dce6b-94c6-4aa3-89ef-25525b4e72db@quicinc.com>
Date: Thu, 11 Apr 2024 16:00:02 +0800
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: ath11k failed to enqueue rx buf: -28
From: Baochen Qiang <quic_bqiang@quicinc.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>,
        James Prestwood
	<prestwoj@gmail.com>,
        "open list:MEDIATEK MT76 WIRELESS LAN DRIVER"
	<linux-wireless@vger.kernel.org>
CC: "ath11k@lists.infradead.org" <ath11k@lists.infradead.org>
References: <5c63a3a2-29fe-444c-96f1-f87c89d7af39@gmail.com>
 <216b223b-e871-42d4-8e53-59dd64efe4b9@quicinc.com>
 <6e8fe8cf-315c-47bb-b8db-5b17f7323109@quicinc.com>
Content-Language: en-US
In-Reply-To: <6e8fe8cf-315c-47bb-b8db-5b17f7323109@quicinc.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit


On 4/1/2024 11:30 AM, Baochen Qiang wrote:
> 
> 
> On 3/30/2024 2:39 AM, Jeff Johnson wrote:
>> On 3/27/2024 9:25 AM, James Prestwood wrote:
>>> Hi,
>>>
>>> This error was brought to my attention in the kernel logs and I'm
>>> wondering if it is of any concern:
>>>
>>> kernel: ath11k_pci 0000:03:00.0: failed to enqueue rx buf: -28
>>>
>>> It seems to happen every few minutes or so. I don't notice any bad
>>> behavior associated with it per-se, but maybe its an issue of some
>>> buffer needing to be increased in size? Does this mean a frame is being
>>> dropped due to no room to receive it?
>>>
>>> Hardware we are running is:
>>>
>>> [    4.610399] ath11k_pci 0000:03:00.0: wcn6855 hw2.1
>>> [    5.777030] ath11k_pci 0000:03:00.0: chip_id 0x12 chip_family 0xb
>>> board_id 0xff soc_id 0x400c1211
>>> [    5.777039] ath11k_pci 0000:03:00.0: fw_version 0x1109996e
>>> fw_build_timestamp 2023-12-19 11:11 fw_build_id
>>> WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36
>>>
>>> Thanks,
>>>
>>> James
Hi James, I was not able to reproduce this issue so wondering if you 
could help reproduce and collect logs for debug. If OK please first 
merge the debug patch which is available in patchwork:

https://patchwork.kernel.org/project/linux-wireless/patch/20240411074812.86700-1-quic_bqiang@quicinc.com/

Please also enable full ath11k log:
	modprobe ath11k debug_mask=0xffffffff
	modprobe ath11k_pci

Once enabled you should see lots of ath11k logs.

>>>
>>>
>>
>> + ath11k list to get more specific eyes on this issue
>> + bcc to internal list as well
>>
> I will look into this.
>>