Kalle Valo <kvalo@xxxxxxxxxxxxxxxx> writes: > Michal Kazior <michal.kazior@xxxxxxxxx> writes: > >> Warm reset was not able to recover from a device >> crash so ath10k was falling back to cold reset >> which would occasionally hang the system or >> generate a data bus error with some device chips. >> >> Warm reset now works a lot more reliably (at least >> on my T430). It's able to recover from a "hard" >> simulate fw crash and some firmware asserts I've >> forced meaning it should recover in most cases >> without falling back to the cold reset. >> >> There's still one case of a crash warm reset is >> incapable to recover from: IOMMU faults (when >> supported and enabled and device tries to access >> non-DMA mapped host memory) trigger device crash >> and leave CE totally unresponsive before and after >> the warm reset. >> >> >> Michal Kazior (2): >> ath10k: improve warm reset reliability >> ath10k: retry warm reset a few times > > The patches don't apply anymore and the conflict was not trivial enough > for me to fix it. Can you rebase, please? Sorry, I replied to the wrong thread. Please ignore what I said above! -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html