From: Klaus Kudielka <klaus.kudielka@gmail.com>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
Jeff Johnson <jjohnson@kernel.org>, Kalle Valo <kvalo@kernel.org>,
Baochen Qiang <quic_bqiang@quicinc.com>,
Baochen Qiang <baochen.qiang@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
linux-kernel@vger.kernel.org,
Paul Menzel <pmenzel@molgen.mpg.de>,
regressions@lists.linux.dev
Subject: [REGRESSION] ath10k fails initialization, bisected to "wifi: ath10k: avoid unnecessary wait for service ready message"
Date: Fri, 17 Oct 2025 17:37:34 +0200 [thread overview]
Message-ID: <6d41bc00602c33ffbf68781f563ff2e6c6915a3e.camel@gmail.com> (raw)
In-Reply-To: <175823924851.3217488.17742065327824732992.b4-ty@oss.qualcomm.com>
On Thu, 2025-09-18 at 16:47 -0700, Jeff Johnson wrote:
>
> On Mon, 11 Aug 2025 17:26:45 +0800, Baochen Qiang wrote:
> > Commit e57b7d62a1b2 ("wifi: ath10k: poll service ready message before
> > failing") works around the failure in waiting for the service ready
> > message by active polling. Note the polling is triggered after initial
> > wait timeout, which means that the wait-till-timeout can not be avoided
> > even the message is ready.
> >
> > A possible fix is to do polling once before wait as well, however this
> > can not handle the race that the message arrives right after polling.
> > So the solution is to do periodic polling until timeout.
> >
> > [...]
>
> Applied, thanks!
>
> [1/1] wifi: ath10k: avoid unnecessary wait for service ready message
> commit: 51a73f1b2e56b0324b4a3bb8cebc4221b5be4c7a
>
> Best regards,
Unfortunately, this particular commit completely breaks the ath10k driver in my setup.
Hardware:
- Turris Omnia (arch/arm/boot/dts/marvell/armada-385-turris-omnia.dts)
- Wifi card (output from lspci): Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter
dmesg output after loading ath10k_pci
[ 5.895939] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 6.152971] ath10k_pci 0000:02:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[ 6.152994] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 1 testmode 0
[ 6.154343] ath10k_pci 0000:02:00.0: firmware ver 10.2.4-1.0-00047 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 35bd9258
[ 6.214165] ath10k_pci 0000:02:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
So far so good, but then come the problematic error messages:
[ 12.509390] ath10k_pci 0000:02:00.0: wmi unified ready event not received
[ 12.580885] ath10k_pci 0000:02:00.0: could not init core (-110)
[ 12.586891] ath10k_pci 0000:02:00.0: could not probe fw (-110)
And the corresponding netdevice does not appear at all.
---
If I revert said commit (on top of current mainline), all is good again:
[ 6.112174] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 6.264184] ath10k_pci 0000:02:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[ 6.264199] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 1 testmode 0
[ 6.265591] ath10k_pci 0000:02:00.0: firmware ver 10.2.4-1.0-00047 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 35bd9258
[ 6.298955] ath10k_pci 0000:02:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[ 7.458285] ath10k_pci 0000:02:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
[ 8.910074] ath10k_pci 0000:02:00.0: pdev param 0 not supported by firmware
[ 8.934074] ath10k_pci 0000:02:00.0 wlan1: entered allmulticast mode
[ 8.934187] ath10k_pci 0000:02:00.0 wlan1: entered promiscuous mode
Best regards, Klaus
#regzbot introduced: 51a73f1b2e56b0324b4a3bb8cebc4221b5be4c7a ("wifi: ath10k: avoid unnecessary wait for service ready message")
next prev parent reply other threads:[~2025-10-17 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 9:26 [PATCH ath-next] wifi: ath10k: avoid unnecessary wait for service ready message Baochen Qiang
2025-09-18 7:27 ` Vasanthakumar Thiagarajan
2025-09-18 23:47 ` Jeff Johnson
2025-10-17 15:37 ` Klaus Kudielka [this message]
2025-10-17 15:57 ` [REGRESSION] ath10k fails initialization, bisected to "wifi: ath10k: avoid unnecessary wait for service ready message" Jeff Johnson
2025-10-18 13:50 ` Klaus Kudielka
2025-10-22 8:00 ` Baochen Qiang
2025-10-22 17:30 ` Klaus Kudielka
2025-10-01 6:22 ` [PATCH ath-next] wifi: ath10k: avoid unnecessary wait for service ready message Paul Menzel
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=6d41bc00602c33ffbf68781f563ff2e6c6915a3e.camel@gmail.com \
--to=klaus.kudielka@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=quic_bqiang@quicinc.com \
--cc=regressions@lists.linux.dev \
/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 NNTP newsgroup(s).