Bug 214455
| Summary: | Kernel 5.14.5 ath11k/mhi regression: Wifi stops working | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | D.F. (dominik.foerderer) |
| Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
| Status: | RESOLVED CODE_FIX | ||
| Severity: | blocking | CC: | dominik.foerderer, error27, ivo.mavrud, jan.hicken, kvalo, kvalo, philm, sander, tjw.ward, yyc1992 |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 5.14.5, 5.13.18 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
|
Description
D.F.
2021-09-17 12:33:38 UTC
Starting my system with Kernel 5.13.18 shows, that this one is also affected with the same error message. The last known working 5.13 Kernel was 5.13.15 i guess. I found out that the regression is caused by commit 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter After reverting this commit in 5.14.5 or 5.13.18 everything is fine and Wifi is working. I ran into the same problem on my Dell XPS 9500, which also has the Qualcomm Atheros QCA6390 (Killer AX500) Wi-Fi card installed. I can confirm that reverting the commit 3f38cc1ba1e289306f52cb7238406f38ecbfa21a fixes the error and makes the ath11k driver work again. Dan Carpenter, it's your patch, could you check it please? This should fix this: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/patch/net/qrtr?id=d2cabd2dc8da78faf9b690ea521d03776686c9fe Don't want to recompile the kernel. Is it going to be fixed in the next release? 5.14.6 is still not good. Cheers! Ivo Linus' tree is ok, this is a problem with stable kernels. Someone please report this to stable tree maintainers so that they include the fix to stable trees. Closing the bug report as upstream is ok. Will be fixed in the upcoming 5.14.7 release. 5.13 series won't get that fix. Distros might need to backport if they continue that EOL marked kernel series: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.14/net-qrtr-revert-check-in-qrtr_endpoint_post.patch Not sure if this is the expected behavior of the issue but I've also observed that the card is missing from the PCIe bus on the next boot after this happens. Resetting and removing the bridge connecting to the network card seems to work for me to make the device appear again. (On XPS 15 9500, the network card is on 6c:00.0 and the bridge to it is at 00.1c.5). (In reply to Philip Müller from comment #8) > Will be fixed in the upcoming 5.14.7 release. 5.13 series won't get that > fix. Distros might need to backport if they continue that EOL marked kernel > series: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/ > queue-5.14/net-qrtr-revert-check-in-qrtr_endpoint_post.patch Thanks. I don't think this same issue exists in 5.13 series. All trees still need to reserve memory range explicitly in the kern param. I stumbled across this topic when my AX500 wifi card on the dell XPS13 9310 stopped working after an update on OpenSUSE tumbleweed. Similar to the above comments, the card no longer appeared in lspci output and revering to the older kernel did not work immediately. I had to disable the chip in bios, reboot, and re-enable before the card would be recognized by the system again. (In reply to Yichao Yu from comment #9) > Not sure if this is the expected behavior of the issue but I've also > observed that the card is missing from the PCIe bus on the next boot after > this happens. > Resetting and removing the bridge connecting to the network card seems to > work for me to make the device appear again. (On XPS 15 9500, the network > card is on 6c:00.0 and the bridge to it is at 00.1c.5). One issue per bug report, please. Otherwise bugzilla becomes a nightmare to maintain. Please file a new bug: https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport |