Hi Jakub et al, On Wed, 2020-12-09 at 09:13 -0800, Jakub Kicinski wrote: > On Tue, 8 Dec 2020 23:17:48 +0000 Rui Salvaterra wrote: > > Hi, Luca, > > > > On Tue, 8 Dec 2020 at 16:27, Coelho, Luciano <luciano.coelho@xxxxxxxxx> wrote: > > > On Tue, 2020-12-08 at 11:27 +0000, Rui Salvaterra wrote: > > > > > > > > [ 3174.003910] iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio. > > > > [ 3174.003913] iwlwifi 0000:02:00.0: reporting RF_KILL (radio disabled) > > > > > > It looks like your machine is reporting RF-Kill to the WiFi device. > > > > Yes, that's an artifact of how I tested: I rebooted the router, the > > Wi-Fi interface disassociated and the dmesg was clean. However, after > > the router came up, the laptop didn't reconnect (and the connection > > had completely disappeared from nmtui). Afterwards, I did the rfkill > > cycle you see, and only then I got the register dump. > > > > > There seems to be some sort of race there that is causing us to still > > > try to communicate with the device (and thus you see the transaction > > > failed dump), but that will obviously fail when RF-Kill is enabled. > > > > I'm not sure about that, the card was already dead before the rfkill cycle. > > Any luck figuring this out, Luca? If this is a 5.10 regression we need > to let Linus know tomorrow, so the time is ticking :( I just checked all the commits in iwlwifi between v5.9 and v5.10 and I don't see anything that could affect how RF-Kill works. Emmanuel, do you remember anything that went in that could have affected RF-Kill? -- Cheers, Luca.
