From: Kalle Valo <kvalo@kernel.org>
To: Peter Dohm <peterdohm@blackmesa.com>
Cc: "ath10k\@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Odd crash in ath10k card only on certain firmware versions...
Date: Wed, 05 Apr 2023 16:39:40 +0300 [thread overview]
Message-ID: <874jpua1nn.fsf@kernel.org> (raw)
In-Reply-To: <IA0PR20MB5731A6A9BAFB17E886DF2097B0889@IA0PR20MB5731.namprd20.prod.outlook.com> (Peter Dohm's message of "Tue, 28 Mar 2023 20:56:33 +0000")
Peter Dohm <peterdohm@blackmesa.com> writes:
> I’ve been experimenting with a generic QCA6174 hw 3.0 card that was
> purchased with my Protectli Vault appliance
> (https://protectli.com/product/m2-wifi/) which looks to just be this
> device resold: https://www.jetone.com.tw/jww6051.html
>
> The device per lspci looks like so:
>
> 07:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
> Network Adapter (rev 30)
> Subsystem: Qualcomm Atheros Device 3361
> Flags: bus master, fast devsel, latency 0, IRQ 176
> Memory at b1000000 (64-bit, non-prefetchable) [size=2M]
> Capabilities: [40] Power Management version 3
> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
> Capabilities: [70] Express Endpoint, MSI 00
> Capabilities: [100] Advanced Error Reporting
> Capabilities: [148] Virtual Channel
> Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
> Capabilities: [178] Latency Tolerance Reporting
> Capabilities: [180] L1 PM Substates
> Kernel driver in use: ath10k_pci
> Kernel modules: ath10k_pci
>
> This is an arch linux kernel: 6.2.8-arch1-1#1 SMP PREEMPTY_DYNAMIC,
> and everything is the latest generally available as per the date of
> this original email, March 28, 2023.
>
> The default linux firmware that ships with arch (which uses the latest
> per hashes of the latest available on github) crashes as i’ll describe
> below...
>
> If I use firmware version
> QCA6174/hw3.0/4.4.1/firmware-6.bin_WLAN.RM.4.4.1-00132-QCARMSWP-1,
> everything works perfectly. If i use any firmware newer than version
> 00132, i get the following crash during in module load:
>
> (these are the only dmesg lines emitted, and the adapter interface does not plumb)
>
> [timestamp] ath10k_pci 0000:07:00.0: wmi unified ready event not received
> [timestamp] ath10k_pci 0000:07:00.0: device has crashed during init
> [timestamp] ath10k_pci 0000:07:00.0: device has crashed during init
> [timestamp] ath10k_pci 0000:07:00.0: failed to wait for target init: -70
> [timestamp] ath10k_pci 0000:07:00.0: could not init core (-110)
> [timestamp] ath10k_pci 0000:07:00.0: could not probe fw (-110)
>
> Does anyone have ANY ideas why this particular card is crashing on the
> most recent firmwares? I am glad to experiment to try and figure this
> out with others’ help.
There was a similar thread already from last year, I'll include you to
that thread:
https://lore.kernel.org/ath10k/878rf6a1s2.fsf@kernel.org/T/#t
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2023-04-05 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 20:56 Odd crash in ath10k card only on certain firmware versions Peter Dohm
2023-04-05 13:39 ` 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=874jpua1nn.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=peterdohm@blackmesa.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