From: Larry Finger <Larry.Finger@lwfinger.net>
To: Sean Paul <seanpaul@google.com>
Cc: Brett Rudley <brudley@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: brcm80211 locking up
Date: Mon, 13 Dec 2010 12:33:47 -0600 [thread overview]
Message-ID: <4D06670B.90200@lwfinger.net> (raw)
In-Reply-To: <AANLkTikL8M-nbCuhj4UmYVYEX-5ba2rRthTMFqbYqmwp@mail.gmail.com>
On 12/13/2010 12:22 PM, Sean Paul wrote:
> Hey Brett,
> I've checked the switch, it's enabled. I've also tried the code on a
> different machine (same model) with the same result.
>
> Sean
>
> On Mon, Dec 13, 2010 at 10:21 AM, Brett Rudley <brudley@broadcom.com> wrote:
>> Check the RF disable switch on your laptop (also known as airline switch, wireless disable switch, etc).
>> It probably got bumped to the 'disabled' position.
I have noticed some instances where a new kernel will come up with rfkill hard
blocked even when the switch is in the on position, and in one case where the
box does not even have a switch. These have been with b43, thus no hang.
Unloading/reloading the driver fixes the issue, which I think is caused by an
uninitialized variable in rfkill. Thus far, I have not found a cause, and have
not previously reported it.
In any case, booting the computer with the rf switch off should not cause an
infinite loop.
Larry
next prev parent reply other threads:[~2010-12-13 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 18:02 brcm80211 locking up Sean Paul
2010-12-13 18:21 ` Brett Rudley
2010-12-13 18:22 ` Sean Paul
2010-12-13 18:33 ` Larry Finger [this message]
2010-12-13 18:38 ` Sean Paul
2010-12-13 19:32 ` Brett Rudley
2010-12-14 14:26 ` Sean Paul
2010-12-14 20:04 ` Sean Paul
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=4D06670B.90200@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=brudley@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=seanpaul@google.com \
/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