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: Tue, 19 Dec 2023 20:24:25 +0200 [thread overview]
Message-ID: <87edfiqcdi.fsf@kernel.org> (raw)
In-Reply-To: <ab00ff77-23de-43a1-9eb9-6ac036ab80e3@gmail.com> (James Prestwood's message of "Tue, 19 Dec 2023 05:51:24 -0800")
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.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-12-19 18:24 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 [this message]
2023-12-20 12:42 ` James Prestwood
2023-12-20 14:30 ` Kalle Valo
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=87edfiqcdi.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