From: Kalle Valo <kvalo@kernel.org>
To: James Prestwood <prestwoj@gmail.com>
Cc: "open list:MEDIATEK MT76 WIRELESS LAN DRIVER"
<linux-wireless@vger.kernel.org>,
ath11k@lists.infradead.org
Subject: Re: Ath11k warnings, and eventual phy going away requiring reboot
Date: Wed, 20 Dec 2023 16:30:54 +0200 [thread overview]
Message-ID: <87o7elosip.fsf@kernel.org> (raw)
In-Reply-To: <6122eb4e-66f5-4772-b211-8fc69ac88ebe@gmail.com> (James Prestwood's message of "Wed, 20 Dec 2023 04:42:31 -0800")
James Prestwood <prestwoj@gmail.com> writes:
> Hi Kalle,
>
> On 12/19/23 10:24 AM, Kalle Valo wrote:
>> James Prestwood <prestwoj@gmail.com> writes:
>>
>>> I noticed this after one of our devices dropped offline. The device
>>> had roamed 7 minutes prior so I doubt that had anything to do with it.
>>> But then we get this, and then tons of warnings. I'm happy to provide
>>> full stack traces but its quite a few, not sure which ones are
>>> relevant or not. After all the warnings IWD got an RTNL del link event
>>> and was unable to recover from that. It seems after that ath11k tried
>>> to power back on but failed.
>>>
>>> This is a stock 6.2 ubuntu kernel, WCN6855:
>> BTW I don't know how it's nowadays, but back in the day Ubuntu heavily
>> modified ath11k. And we can't support distro kernels anyway as we don't
>> know what they have changed in the kernel.
>
> Ok. I understand where your coming from, but at the same time Ubuntu
> is the largest linux distribution so it seems like these type of
> reports wouldn't be uncommon. OTOH maybe users just go directly to
> Ubuntu.
Isn't the recommendation that distro kernel bugs should be reported to
distro bug trackers? At least that's what I have understood. At least
our bugzilla says that:
https://bugzilla.kernel.org/
> Anyways, this is a list of patches isn't huge according to the
> changelog (for 6.2):
>
> - wifi: ath11k: fix registration of 6Ghz-only phy without the
> full channel
> - wifi: ath11k: add support default regdb while searching
> board-2.bin for
> - wifi: ath11k: fix memory leak in WMI firmware stats
> - wifi: ath11k: Add missing check for ioremap
> - wifi: ath11k: Ignore frags from uninitialized peer in dp.
> - wifi: ath11k: Fix SKB corruption in REO destination ring
> - wifi: ath11k: reduce the MHI timeout to 20s
> - wifi: ath11k: Use platform_get_irq() to get the interrupt
> - wifi: ath11k: fix SAC bug on peer addition with sta band migration
> - wifi: ath11k: fix deinitialization of firmware resources
> - wifi: ath11k: fix writing to unintended memory region
> - wifi: ath11k: Fix memory leak in ath11k_peer_rx_frag_setup
> - wifi: ath11k: fix monitor mode bringup crash
> - wifi: ath11k: debugfs: fix to work with multiple PCI devices
> - wifi: ath11k: allow system suspend to survive ath11k
>
> I see the dilemma of not wanting to waste time debugging when there
> are unknown changes applied. I was hoping someone would recognize the
> behavior and could suggest a patch/kernel/firmware to try
Sure, I also get where you are coming from :) Just wanted to make sure
you know the problem with distro kernels.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2023-12-20 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 13:51 Ath11k warnings, and eventual phy going away requiring reboot James Prestwood
2023-12-19 18:24 ` Kalle Valo
2023-12-20 12:42 ` James Prestwood
2023-12-20 14:30 ` Kalle Valo [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=87o7elosip.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=prestwoj@gmail.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).