Same reported by Xell Kim yesterday:

https://lore.kernel.org/all/87ee3yzo7v.fsf@kernel.org/T/

same problem.

Kalle, am I correctly understand, that fix will be bundled someday to https://github.com/kvalo/ath11k-firmware and we should subscribe to it?

Crossing fingers, we need here only firmware and not kernel changes )

(In reply to Alexander Ustimenko from comment #3)
> Kalle, am I correctly understand, that fix will be bundled someday to
> https://github.com/kvalo/ath11k-firmware

Correct. I'm currently trying to find a correct board file this device and will upload once I have it. I will also notify here.

> Crossing fingers, we need here only firmware and not kernel changes )

With WCN6855 I recommend using kernel v5.17. Older might work but I have not tested those.

I've done some experiments and may find something weird. As for the
reboot problem I mentioned in the previous email, I filed a new bug
report in https://bugzilla.kernel.org/show_bug.cgi?id=215630 and will
briefly describe it here as it may be solved with this problem
together.

kernel 5.17.rc3.22020 with blacklist ath11k:
dmesg | grep ath:
kernel 5.17-rc3 [ 0.950236] systemd[1]: File System Check on Root
Device was skipped because of a failed condition check
(ConditionPathIsReadWrite=!/).

kernel 5.17.rc3.22020 with ath11k not in the black list (this message
may vary due to info below)
systemd[1]: File System Check on Root Device was skipped because of a
failed condition check (ConditionPathIsReadWrite=!/).
[ 2.371973] ath11k_pci 0000:02:00.0: BAR 0: assigned [mem
0xd1000000-0xd11fffff 64bit]
[ 2.371991] ath11k_pci 0000:02:00.0: enabling device (0000 -> 0002)
[ 2.372328] ath11k_pci 0000:02:00.0: MSI vectors: 32
[ 2.372332] ath11k_pci 0000:02:00.0: wcn6855 hw2.0

For Kernel 5.17rc3, when ath11k is in the blacklist, I can reboot the
system in normal speed, but when ath11k is not in the blacklist, the
reboot will be in very slow speed.

kernel:5.15-16-1 with blacklist ath11k
sudo dmesg | grep ath
[ 0.950236] systemd[1]: File System Check on Root Device was skipped
because of a failed condition check (ConditionPathIsReadWrite=!/).
[ 1.013302] systemd[1]: Virtual Machine and Container Storage
(Compatibility) was skipped because of a failed condition check
(ConditionPathExists=/var/lib/machines.raw).

kernel:5.15-16-1 removing ath11k from blacklist:
sudo dmesg | grep ath
[ 1.000532] systemd[1]: File System Check on Root Device was skipped
because of a failed condition check (ConditionPathIsReadWrite=!/).
[ 1.053473] systemd[1]: Virtual Machine and Container Storage
(Compatibility) was skipped because of a failed condition check
(ConditionPathExists=/var/lib/machines.raw).
[ 1.874492] ath11k_pci 0000:02:00.0: BAR 0: assigned [mem
0xd1000000-0xd11fffff 64bit]
[ 1.874509] ath11k_pci 0000:02:00.0: enabling device (0000 -> 0002)
[ 1.874844] ath11k_pci 0000:02:00.0: wcn6855 hw2.0
[ 2.707262] Modules linked in: pcc_cpufreq(-) qrtr_mhi cmac algif_hash
algif_skcipher af_alg bnep vfat fat uvcvideo qrtr videobuf2_vmalloc
videobuf2_memops ns videobuf2_v4l2 btusb ath11k_pci videobuf2_common
btrtl intel_rapl_msr btbcm intel_rapl_common ath11k videodev btintel
joydev bluetooth qmi_helpers mc mousedev ecdh_generic uinput amdgpu(+)
edac_mce_amd mac80211 kvm_amd snd_hda_codec_hdmi
snd_hda_codec_conexant snd_hda_codec_generic huawei_wmi snd_hda_intel
libarc4 ledtrig_audio hid_multitouch wmi_bmof sparse_keymap kvm
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec irqbypass
crct10dif_pclmul cfg80211 snd_hda_core crc32_pclmul snd_hwdep
ghash_clmulni_intel snd_pcm aesni_intel snd_timer crypto_simd
snd_pci_acp5x gpu_sched sp5100_tco snd cryptd snd_rn_pci_acp3x rfkill
drm_ttm_helper pcspkr mhi snd_pci_acp3x tpm_crb ccp ttm soundcore
i2c_piix4 k10temp rapl mac_hid tpm_tis tpm_tis_core tpm video
i2c_hid_acpi wmi i2c_hid rng_core amd_pmc pinctrl_amd acpi_cpufreq
squashfs loop
[ 2.707447] ath11k_qmi_msg_mem_request_cb+0x1b6/0x310 [ath11k
3e52950f3f35c569855b5df38e8a9b123f0c17c4]
[ 2.715057] ath11k_pci 0000:02:00.0: chip_id 0x2 chip_family 0xb
board_id 0xff soc_id 0x400c0200
[ 2.715068] ath11k_pci 0000:02:00.0: fw_version 0x110d8c35
fw_build_timestamp 2022-01-27 04:01 fw_build_id
QC_IMAGE_VERSION_STRING=WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3
[ 2.717265] ath11k_pci 0000:02:00.0: failed to fetch board data for
bus=pci,qmi-chip-id=2,qmi-board-id=255 from
ath11k/WCN6855/hw2.0/board-2.bin
[ 2.928925] ath11k_pci 0000:02:00.0: firmware crashed: MHI_CB_SYS_ERROR
[ 7.808023] ath11k_pci 0000:02:00.0: failed to load board data file: -110

kernel:5.15-16-1 removing ath11k from blacklist after reboot:
sudo dmesg | grep ath (yes the message changed. And I assume that the
same thing can also occur under kernel 5.17rc3)
[ 0.999917] systemd[1]: File System Check on Root Device was skipped
because of a failed condition check (ConditionPathIsReadWrite=!/).
[ 1.059134] systemd[1]: Virtual Machine and Container Storage
(Compatibility) was skipped because of a failed condition check
(ConditionPathExists=/var/lib/machines.raw).
[ 1.883741] ath11k_pci 0000:02:00.0: BAR 0: assigned [mem
0xd1000000-0xd11fffff 64bit]
[ 1.883767] ath11k_pci 0000:02:00.0: enabling device (0000 -> 0002) [
1.884266] ath11k_pci 0000:02:00.0: wcn6855 hw2.0

kernel 5.10.98 - 1: with ath11k in or not in the blacklist (the most
weird thing)
[    1.027027] systemd[1]: File System Check on Root Device was
skipped because of a failed condition check
(ConditionPathIsReadWrite=!/).
[    1.087394] systemd[1]: Virtual Machine and Container Storage
(Compatibility) was skipped because of a failed condition check
(ConditionPathExists=/var/lib/machines.raw).

When I use the kernel 5.10 the problem with the board file seems to
disappear. There may be some other problems with my system.

kernel 5.15 and kernel 5.10.98-1, with ath11k in or not in the
blacklist: reboot in normal speed.

Kalle, thank you for posting update at https://github.com/kvalo/ath11k-firmware/commit/a31b1a6e0032415dc3b0bdf9955fc7a1e63bd3ce

I pulled it and wi-fi now works out of the box.

> Kalle, thank you for posting update at
>
> https://github.com/kvalo/ath11k-firmware/commit/a31b1a6e0032415dc3b0bdf9955fc7a1e63bd3ce
>
> I pulled it and wi-fi now works out of the box.

Great, thanks for closing the bug.

It works for me too! Thanks a lot.