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>
Subject: Re: ath11k failed to enqueue rx buf: -28
Date: Thu, 11 Apr 2024 16:00:02 +0800 [thread overview]
Message-ID: <347dce6b-94c6-4aa3-89ef-25525b4e72db@quicinc.com> (raw)
In-Reply-To: <6e8fe8cf-315c-47bb-b8db-5b17f7323109@quicinc.com>
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.
>>
next prev parent reply other threads:[~2024-04-11 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 16:25 ath11k failed to enqueue rx buf: -28 James Prestwood
2024-03-28 14:37 ` James Prestwood
2024-03-29 18:39 ` Jeff Johnson
2024-04-01 3:30 ` Baochen Qiang
2024-04-11 8:00 ` Baochen Qiang [this message]
2024-04-16 12:50 ` James Prestwood
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=347dce6b-94c6-4aa3-89ef-25525b4e72db@quicinc.com \
--to=quic_bqiang@quicinc.com \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=prestwoj@gmail.com \
--cc=quic_jjohnson@quicinc.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).