2010-07-01 03:00:07

by Andrew Lutomirski

[permalink] [raw]
Subject: rfkill failure in 2.6.35-rc3+

I just toggled rfkill on and back off on my X200s (WiFi Link 5350, rev
0x24) and the link didn't come up. Toggling rfkill again didn't fix
it, but rmmod + modprobe did.

dmesg said:

[13629.424869] iwlagn 0000:03:00.0: RF_KILL bit toggled to disable radio.
[13629.432761] iwlagn 0000:03:00.0: Not sending command - RF KILL
[13629.432771] iwlagn 0000:03:00.0: Error sending REPLY_RXON:
enqueue_hcmd failed: -5
[13629.432778] iwlagn 0000:03:00.0: Error setting new RXON (-5)
[13631.268646] iwlagn 0000:03:00.0: RF_KILL bit toggled to enable radio.
[13631.311232] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[13675.710821] iwlagn 0000:03:00.0: RF_KILL bit toggled to disable radio.
[13675.713438] iwlagn 0000:03:00.0: Not sending command - RF KILL
[13675.713448] iwlagn 0000:03:00.0: Error sending REPLY_RXON:
enqueue_hcmd failed: -5
[13675.713455] iwlagn 0000:03:00.0: Error setting new RXON (-5)
[13683.090789] iwlagn 0000:03:00.0: RF_KILL bit toggled to enable radio.
[13683.145267] ADDRCONF(NETDEV_UP): wlan0: link is not ready

This is 2.6.35-rc3+ with firmware 8.24.2.12. I've never seen this before.


2010-07-01 15:59:44

by Reinette Chatre

[permalink] [raw]
Subject: Re: rfkill failure in 2.6.35-rc3+

On Wed, 2010-06-30 at 19:59 -0700, Andrew Lutomirski wrote:
> I just toggled rfkill on and back off on my X200s (WiFi Link 5350, rev
> 0x24) and the link didn't come up. Toggling rfkill again didn't fix
> it, but rmmod + modprobe did.
>
> dmesg said:
>
> [13629.424869] iwlagn 0000:03:00.0: RF_KILL bit toggled to disable radio.
> [13629.432761] iwlagn 0000:03:00.0: Not sending command - RF KILL
> [13629.432771] iwlagn 0000:03:00.0: Error sending REPLY_RXON:
> enqueue_hcmd failed: -5
> [13629.432778] iwlagn 0000:03:00.0: Error setting new RXON (-5)
> [13631.268646] iwlagn 0000:03:00.0: RF_KILL bit toggled to enable radio.
> [13631.311232] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [13675.710821] iwlagn 0000:03:00.0: RF_KILL bit toggled to disable radio.
> [13675.713438] iwlagn 0000:03:00.0: Not sending command - RF KILL
> [13675.713448] iwlagn 0000:03:00.0: Error sending REPLY_RXON:
> enqueue_hcmd failed: -5
> [13675.713455] iwlagn 0000:03:00.0: Error setting new RXON (-5)
> [13683.090789] iwlagn 0000:03:00.0: RF_KILL bit toggled to enable radio.
> [13683.145267] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>
> This is 2.6.35-rc3+ with firmware 8.24.2.12. I've never seen this before.

Recently we have seen a few issues with rfkill state changes not being
seen by the driver. In all cases it was "resolved" by unloading (or not
loading from the beginning via blacklisting) of the platform driver. Can
you try that?

Reinette



2010-07-16 15:00:08

by Andrew Lutomirski

[permalink] [raw]
Subject: Re: rfkill failure in 2.6.35-rc3+

I haven't been able to reproduce this, so I haven't tried unloading
the platform driver. I will if it happens again, though.

--Andy

On Thu, Jul 1, 2010 at 11:59 AM, reinette chatre
<[email protected]> wrote:
> On Wed, 2010-06-30 at 19:59 -0700, Andrew Lutomirski wrote:
>> I just toggled rfkill on and back off on my X200s (WiFi Link 5350, rev
>> 0x24) and the link didn't come up. ?Toggling rfkill again didn't fix
>> it, but rmmod + modprobe did.
>>
>> dmesg said:
>>
>> [13629.424869] iwlagn 0000:03:00.0: RF_KILL bit toggled to disable radio.
>> [13629.432761] iwlagn 0000:03:00.0: Not sending command - RF KILL
>> [13629.432771] iwlagn 0000:03:00.0: Error sending REPLY_RXON:
>> enqueue_hcmd failed: -5
>> [13629.432778] iwlagn 0000:03:00.0: Error setting new RXON (-5)
>> [13631.268646] iwlagn 0000:03:00.0: RF_KILL bit toggled to enable radio.
>> [13631.311232] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>> [13675.710821] iwlagn 0000:03:00.0: RF_KILL bit toggled to disable radio.
>> [13675.713438] iwlagn 0000:03:00.0: Not sending command - RF KILL
>> [13675.713448] iwlagn 0000:03:00.0: Error sending REPLY_RXON:
>> enqueue_hcmd failed: -5
>> [13675.713455] iwlagn 0000:03:00.0: Error setting new RXON (-5)
>> [13683.090789] iwlagn 0000:03:00.0: RF_KILL bit toggled to enable radio.
>> [13683.145267] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>>
>> This is 2.6.35-rc3+ with firmware 8.24.2.12. ?I've never seen this before.
>
> Recently we have seen a few issues with rfkill state changes not being
> seen by the driver. In all cases it was "resolved" by unloading (or not
> loading from the beginning via blacklisting) of the platform driver. Can
> you try that?
>
> Reinette
>
>
>