From: reinette chatre <reinette.chatre@intel.com>
To: Andrew Lutomirski <andy@luto.us>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ilw@linux.intel.com" <ilw@linux.intel.com>
Subject: Re: rfkill failure in 2.6.35-rc3+
Date: Thu, 01 Jul 2010 08:59:27 -0700 [thread overview]
Message-ID: <1277999967.4197.92.camel@rchatre-DESK> (raw)
In-Reply-To: <AANLkTikqJzkFFtmOowq-OzzDFSC9_1SFuAfT4UGZBhqW@mail.gmail.com>
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
next prev parent reply other threads:[~2010-07-01 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 2:59 rfkill failure in 2.6.35-rc3+ Andrew Lutomirski
2010-07-01 15:59 ` reinette chatre [this message]
2010-07-16 14:59 ` Andrew Lutomirski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1277999967.4197.92.camel@rchatre-DESK \
--to=reinette.chatre@intel.com \
--cc=andy@luto.us \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox