On 27 July 2015 at 22:08, Enrico Tagliavini <enrico.tagliavini@xxxxxxxxx> wrote: > Hello there, > > I gave 4.2 rc3 a shot and I discovered the wireless was not working > anymore with it. I tried adding irq_mode=1 alongside skip_otp=y in > ath10k_core (I assume you need fw api 5 to remove this, is that > correct?, I still have fw 4 only). > > Loading with irq_mode=0 > > [ 21.130224] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002) > [ 21.130734] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8 > irq_mode 0 reset_mode 0 There was already a similar report[1]. Just for the record: what number of interrupts did you have before 4.2-rc3? I assume it was "pci irq msi interrupts 1 irq_mode 0 reset_mode 0". My suspicion is that either the firmware is buggy and doesn't play well with multiple MSI interrupts or the MSI interrupt behaviour changed significantly (compared to qca988x) and this remained hidden because not an awful lot of machines seemed to have provided more than 1 msi interrupt for ath10k. [1]: http://lists.infradead.org/pipermail/ath10k/2015-July/005695.html Michał -- 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
