From: Larry Finger <Larry.Finger@lwfinger.net>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
wey-yi.w.guy@intel.com
Subject: Re: iwl rfkill suddenly dropped to hard block
Date: Wed, 15 Dec 2010 22:23:32 -0600 [thread overview]
Message-ID: <4D099444.5040703@lwfinger.net> (raw)
In-Reply-To: <20101216032247.GA7345@ioremap.net>
On 12/15/2010 09:22 PM, Evgeniy Polyakov wrote:
> On Wed, Dec 15, 2010 at 03:11:27PM -0500, John W. Linville (linville@tuxdriver.com) wrote:
>> Cc'ing linux-wireless and Wey-Yi...
>>
>> To be honest, nearly every report of "suddenly my rfkill is stuck
>> on" is because the laptop has multiple rfkill keys, usually with
>> one of them a slider along the edge of the case. In particular,
>> Thinkpads have such switches. The slider gets accidently engaged
>> (possibly while the laptop is being transported or somesuch) and
>> suddenly wireless stops working.
>>
>> Please check for the above. If you are sure that isn't the case, then
>> please try to determine the last working kernel and do a bisection --
>> hopefully you don't have to go all the way back to 2.6.33!
>
> I'm pretty sure it would be that simple if there was such a slider.
>
> There is no way I can bisect this problem since, first, i915 does not
> work anywhere after 2.6.34 upto current git tree, and second, because
> wifi perfectly well worked two days ago with this kernel, and now there
> are no good and bad kernels, only bad ones.
>
> Turning on dell_wmi brings 2 more rfkill classes, which are both
> hard and soft blocked. Both can not be unblocked (even soft unblock),
> although reported case can be soft unblocked (hard block status
> obviously does not change). Actually by default it is soft unblocked,
> other two (another wifi switch and bluetooth) are both hard and soft
> blocked.
>
> I would imagine this is just related to some dellish crap, but I saw a
> number of exactly the same cases in the web including linux-kernel mail
> lists in the past and also without 'slider on the back' case.
I doubt that it is Dell related, if that is what "dellish" means.
I have had some success in clearing this problem by unloading and reloading the
wireless driver. I had the problem on one box that has no rfkill switch and an
802.11b card that uses b43legacy.
Larry
next prev parent reply other threads:[~2010-12-16 4:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101215195651.GA18545@ioremap.net>
2010-12-15 20:11 ` iwl rfkill suddenly dropped to hard block John W. Linville
2010-12-15 20:28 ` Guy, Wey-Yi
2010-12-16 3:22 ` Evgeniy Polyakov
2010-12-16 4:23 ` Larry Finger [this message]
2010-12-16 11:57 ` Evgeniy Polyakov
2010-12-16 14:40 ` Evgeniy Polyakov
2010-12-16 14:42 ` John W. Linville
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=4D099444.5040703@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=wey-yi.w.guy@intel.com \
--cc=zbr@ioremap.net \
/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;
as well as URLs for NNTP newsgroup(s).