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: Mon, 16 May 2022 16:01:00 +0300 [thread overview]
Message-ID: <87sfp94ooj.fsf@kernel.org> (raw)
In-Reply-To: <08d0ec20-f9ae-c546-becb-a77404e91a9a@linaro.org> (Dmitry Baryshkov's message of "Thu, 12 May 2022 22:48:05 +0300")
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:
> On 12/05/2022 21:23, Kalle Valo wrote:
>> 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)
>
> I have asked for the hw details. The user guide for the HDK8450 lists
> WCN6856 chip and also mentions 'Qualcomm® FastConnect™ 6900 Systems'.
So the chip was included within HDK8450? It was not installed to the
board separately or anything like that?
>> And what
>> board file are you using? md5sums of all firmware files is the best.
>
> # md5sum /lib/firmware/ath11k/WCN6855/hw2.1/*
> 460fbd5ddc57b3d2efbf1ca976f78b90
> /lib/firmware/ath11k/WCN6855/hw2.1/amss.bin
> 88b3a4fbde8cab4493f0060ae3b5dee3
> /lib/firmware/ath11k/WCN6855/hw2.1/board-2.bin
> 7fd1c2337b0b6502588d3141e205e735
> /lib/firmware/ath11k/WCN6855/hw2.1/board.bin
> d1460fc1c4595d0d22f82d5baeaabbd8 /lib/firmware/ath11k/WCN6855/hw2.1/m3.bin
> f67be83659c790fe15d1e42af501e9fa
> /lib/firmware/ath11k/WCN6855/hw2.1/regdb.bin
So you are using a separate board.bin file, where did you get it? ath11k
board files are different so you cannot take the board file from
elsewhere.
Can you file this to bugzilla:
https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
That way it's easier to track and I can try to find the correct board
file.
--
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
next prev parent reply other threads:[~2022-05-16 13:08 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
2022-05-12 19:48 ` Dmitry Baryshkov
2022-05-16 13:01 ` Kalle Valo [this message]
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=87sfp94ooj.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.