Linux wireless drivers development
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
	Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: New warning `ath10k_pci 0000:3a:00.0: not found station for peer stats`
Date: Wed, 4 Mar 2026 12:40:22 +0100	[thread overview]
Message-ID: <e1a7dc91-e1c3-42e5-afd8-1e8dc4ff23c6@molgen.mpg.de> (raw)
In-Reply-To: <80231e1b-fc6f-488f-97f7-92e792954022@oss.qualcomm.com>


Dear Baochen,


Thank you for your quick reply.


Am 04.03.26 um 02:47 schrieb Baochen Qiang:
> On 3/4/2026 4:01 AM, Paul Menzel wrote:
>> Am 11.02.26 um 06:43 schrieb Baochen Qiang:
>>> On 2/10/2026 6:31 AM, Paul Menzel wrote:
>>>> Am 09.02.26 um 03:44 schrieb Baochen Qiang:
>>>>> On 2/7/2026 1:55 PM, Paul Menzel wrote:
>>>>>> Am 19.01.26 um 17:41 schrieb Paul Menzel:
>>>>>>
>>>>>>> Since January 10th, I have started seeing the warning below in
>>>>>>> my Linux logs, that reach back to September 24th, 2025:
>>>>>>>
>>>>>>>         [   37.108902] ath10k_pci 0000:3a:00.0: not found station for peer stats
>>>>>>>         [   37.108906] ath10k_pci 0000:3a:00.0: failed to parse stats info tlv: -22
[…]

>>> I managed to reproduce this issue locally. Will submit a patch
>>> fixing it.
>>
>> Sorry for being impatient, but as Linux 7.0-rc2 was tagged, were
>> you able to come up with a patch, or should the commit be reverted
>> for now to have more time to analyze this?
> 
> The patch is under internal review now, will submit once it is
> approved.
Awesome. I am looking forward to it. It’d be great, if you Cc’ed me on 
the patch.


Kind regards,

Paul

      reply	other threads:[~2026-03-04 11:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 16:41 New warning `ath10k_pci 0000:3a:00.0: not found station for peer stats` Paul Menzel
2026-01-20  2:01 ` Baochen Qiang
2026-01-20  2:04   ` Baochen Qiang
2026-02-07  5:55 ` Paul Menzel
2026-02-09  2:44   ` Baochen Qiang
2026-02-09 22:31     ` Paul Menzel
2026-02-11  5:43       ` Baochen Qiang
2026-03-03 20:01         ` Paul Menzel
2026-03-04  1:47           ` Baochen Qiang
2026-03-04 11:40             ` Paul Menzel [this message]

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=e1a7dc91-e1c3-42e5-afd8-1e8dc4ff23c6@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=ath10k@lists.infradead.org \
    --cc=baochen.qiang@oss.qualcomm.com \
    --cc=jjohnson@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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