ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: "ath11k\@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: WCN6855 issues with latest linux-firmware
Date: Thu, 12 May 2022 21:23:52 +0300	[thread overview]
Message-ID: <87v8ua624n.fsf@kernel.org> (raw)
In-Reply-To: <a1657ff0-198c-14f9-3b2b-d7ab06cfc8e6@linaro.org> (Dmitry Baryshkov's message of "Thu, 12 May 2022 17:31:50 +0300")

Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:

> The wcn6855 WiFi chip stopped working for me after an update to the
> latest linux-firmware (Linux 5.18-rc2). I can reproduce it with both
> hw2.0 and hw2.1 chips.
>
> Here is the set of kernel messages I'm getting from ath11k_pci driver:
>
> [    4.422391] ath11k_pci 0000:01:00.0: Adding to iommu group 3
> [    4.429571] ath11k_pci 0000:01:00.0: BAR 0: assigned [mem
> 0x60400000-0x605fffff 64bit]
> [    4.437857] ath11k_pci 0000:01:00.0: enabling device (0000 -> 0002)
> [    4.445323] ath11k_pci 0000:01:00.0: MSI vectors: 1
> [    4.450375] ath11k_pci 0000:01:00.0: wcn6855 hw2.0
> [    5.378488] ath11k_pci 0000:01:00.0: chip_id 0x2 chip_family 0xb
> board_id 0x8c soc_id 0x400c0200
> [    5.392898] ath11k_pci 0000:01:00.0: fw_version 0x110f0c35
> fw_build_timestamp 2022-03-30 09:05 fw_build_id
> QC_IMAGE_VERSION_STRING=WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.7
> [    5.420648] ath11k_pci 0000:01:00.0: failed to fetch board data for
> bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=2,qmi-board-id=140
> from ath11k/WCN6855/hw2.0/board-2.bin
> [   15.686398] ath11k_pci 0000:01:00.0: failed to wait board file
> download request: -110
> [   15.694530] ath11k_pci 0000:01:00.0: qmi failed to load bdf file
> [   15.700784] ath11k_pci 0000:01:00.0: failed to load board data file: -110

What WCN6855 hardware are you exactly using? (make, model etc) And what
board file are you using? md5sums of all firmware files is the best.

> With the earlier firmware from [1] I'm getting the following trace
> (and WiFi device probes). Interestingly enough the chip_id differs
> between these firmware versions.
>
> [    4.352661] ath11k_pci 0000:01:00.0: Adding to iommu group 3
> [    4.359192] ath11k_pci 0000:01:00.0: BAR 0: assigned [mem
> 0x60400000-0x605fffff 64bit]
> [    4.367466] ath11k_pci 0000:01:00.0: enabling device (0000 -> 0002)
> [    4.374916] ath11k_pci 0000:01:00.0: MSI vectors: 1
> [    4.379963] ath11k_pci 0000:01:00.0: wcn6855 hw2.0
> [    5.273930] ath11k_pci 0000:01:00.0: chip_id 0x0 chip_family 0xb
> board_id 0x8c soc_id 0x400c0200
> [    5.286020] ath11k_pci 0000:01:00.0: fw_version 0x110406b8
> fw_build_timestamp 2021-01-08 06:14 fw_build_id
> QC_IMAGE_VERSION_STRING=WLAN.HSP.1.1-01720.1-QCAHSPSWPL_V1_V2_SILICONZ_LITE-1
> [    5.312464] ath11k_pci 0000:01:00.0: failed to fetch board data for
> bus=pci,vendor=17cb,device=1103,subsystem-vendor=17cb,subsystem-device=0108,qmi-chip-id=0,qmi-board-id=140
> from ath11k/WCN6855/hw2.0/board-2.bin
> [    5.384315] ath11k_pci 0000:01:00.0: leaving PCI ASPM disabled to
> avoid MHI M2 problems
>
>
>
> [1]
> https://chromium.googlesource.com/chromiumos/third_party/linux-firmware/+/d233ddd89abe06448070471963a58c0a7da81d79/ath11k/WCN6855/hw2.0

That looks like an unsupported firmware version. I recommend using
_both_ firmwares and board files only from ath11k-firmware.git[1] or
upstream linux-firmware[2].

[1] https://github.com/kvalo/ath11k-firmware

[2] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  reply	other threads:[~2022-05-12 18:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 14:31 WCN6855 issues with latest linux-firmware Dmitry Baryshkov
2022-05-12 18:23 ` Kalle Valo [this message]
2022-05-12 19:48   ` Dmitry Baryshkov
2022-05-16 13:01     ` Kalle Valo
2022-05-16 16:05       ` Dmitry Baryshkov
2022-05-16 16:15         ` Kalle Valo
2022-05-16 16:28           ` Dmitry Baryshkov
2022-05-12 21:08   ` Dmitry Baryshkov
2022-05-14 13:44   ` Dmitry Baryshkov
2022-06-01 12:40 ` Dmitry Baryshkov
2022-06-03  8:36   ` Kalle Valo
2022-06-03  8:40     ` Dmitry Baryshkov
2022-06-03  9:06       ` Kalle Valo
2022-06-03  9:20         ` Dmitry Baryshkov

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=87v8ua624n.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=dmitry.baryshkov@linaro.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