Bug 215998
| Summary: | REGRESSION: ath11k_pci: failed to wait qmi memory request: -110 - Dell XPS 13 9310 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Len Brown (lenb) |
| Component: | network-wireless | Assignee: | Kalle Valo (kvalo) |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | high | ||
| Priority: | P1 | ||
| Hardware: | Intel | ||
| OS: | Linux | ||
| Kernel Version: | 5.18-rc1, 5.18-rc2, 5.18-rc3, 5.18-rc4, 5.18-rc5, 5.18-rc6, 5.18-rc7, 5.18 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
|
Description
Len Brown
2022-05-18 21:32:09 UTC
What firmware version are you using? The best is if you can provide the md5sum of all files: md5sum /lib/firmware/ath11k/QCA6390/hw2.0/* If you are using an older firmware I suspect this is bug #210923. Please try the latest firmware which has a fix for it: https://github.com/kvalo/ath11k-firmware/tree/master/QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-05266-QCAHSTSWPLZ_V2_TO_X86-1 Are suggesting that to update to Linux 5.18 from Linux 5.17, a firmware updated is required? I'm running Ubunto 22.04 LTS, which has this: lenb@lenb-Dell-XPS-13-9310:~$ md5sum /lib/firmware/ath11k/QCA6390/hw2.0/* a101dc90f8e876f39383b60c9da64ec4 /lib/firmware/ath11k/QCA6390/hw2.0/amss.bin 4c0781f659d2b7d6bef10a2e3d457728 /lib/firmware/ath11k/QCA6390/hw2.0/board-2.bin d4c912a3501a3694a3f460d13de06d28 /lib/firmware/ath11k/QCA6390/hw2.0/m3.bin ddc7afcb118def559bf131c3ec2563af /lib/firmware/ath11k/QCA6390/hw2.0/Notice.txt The good news is that 5.18 works with the new firmware: $ md5sum *.bin 682f7ca2e0b3ea16644c3585772a2cba amss.bin fd4aa4a58f33854a751ec7d14d77ce91 m3.bin ath11k_pci 0000:72:00.0: fw_version 0x10121492 fw_build_timestamp 2021-11-04 11:23 fw_build_id The bad news is that Ubuntu 22.04 LTS ships with older firmware: ath11k_pci 0000:72:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id Further, that older firmware works with Linux up through 5.17 and starts failing at Linux 5.18-rc1. So this issue remains to be a Linux kernel regression, and one that real users are going to encounter. > The good news is that 5.18 works with the new firmware: > > $ md5sum *.bin > 682f7ca2e0b3ea16644c3585772a2cba amss.bin > fd4aa4a58f33854a751ec7d14d77ce91 m3.bin Very good, thanks for testing. > ath11k_pci 0000:72:00.0: fw_version 0x10121492 fw_build_timestamp 2021-11-04 > 11:23 fw_build_id > > The bad news is that Ubuntu 22.04 LTS ships with older firmware: > > ath11k_pci 0000:72:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 > 19:50 fw_build_id > > Further, that older firmware works with Linux up through 5.17 and starts > failing at Linux 5.18-rc1. So this issue remains to be a Linux kernel > regression, and one that real users are going to encounter. If the bug you are seeing is really bug #210923, and currently it looks like that's what you are seeing, the bug happens when the buffers allocated by ath11k are under a 32M address limit. So this isn't a regression in v5.18, something just changed enough in you v5.18 builds that the buffers where below that limit and the firmware was crashing. If a firmware update is not possible when one workaround is to use memmap but it's not necessarily reliable: "memmap=12M\$20M" Bad news: routine Ubuntu updates overwrite the hand-updated firmware with old firmware -- making this issue come back. When will Ubuntu have the new ath11k firmware? (In reply to Len Brown from comment #5) > Bad news: routine Ubuntu updates overwrite the hand-updated firmware > with old firmware -- making this issue come back. > > When will Ubuntu have the new ath11k firmware? The fixed firmware is now in linux-firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4a0e59f95830817b1601631281191a5c3327d138 But I don't know when Ubuntu updates their version. As a workaround you might want to consider dpkg's diversion feature, though I have never tried that myself: https://www.debian.org/doc/debian-policy/ap-pkg-diversions.html FWIW, pulling latest ubuntu 22.04.1 update as of today does update linux-firmware, but doesn't seem to yet have this ath11k update. *** This bug has been marked as a duplicate of bug 210923 *** |