On Tue, 2020-12-08 at 11:27 +0000, Rui Salvaterra wrote:
> Hi, everyone,
>
> I'm running Linux 5.10-rc7 with this firmware/hardware:
>
> [ 1.431878] iwlwifi 0000:02:00.0: loaded firmware version
> 29.198743027.0 7265D-29.ucode op_mode iwlmvm
> [ 1.431899] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band
> Wireless AC 3165, REV=0x210
>
> Most of the time, after disabling/enabling Wi-Fi (or, say, rebooting
> the router), the card dies and only comes back after reboot. This is
> the relevant dmesg output:
>
> [ 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.
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.
--
Luca.
Hi, Luca,
On Tue, 8 Dec 2020 at 16:27, Coelho, Luciano <[email protected]> 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.
Thanks,
Rui