linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Poehn <sebastian.poehn@googlemail.com>
To: linux-wireless@vger.kernel.org
Cc: brcm80211-dev-list@broadcom.com
Subject: [BUG] brcmsmac: Invalid killswitch handling
Date: Fri, 24 Aug 2012 10:51:54 +0200	[thread overview]
Message-ID: <1345798314.1478.12.camel@localhost.localdomain> (raw)

I had a discussion with Matthew Garrett about handling of a wifi
killswitch on a Dell laptop.

Some (rfkill) code was removed from platform/dell-laptop. On my machine
a bug now occurs which is caused by brcmsmac in the view of Matthew.

So is this a bug, or do you have no killsitch handling, so far?

Bug description:
> physical switch is OFF
> rfkill state is ON
> => Laptop hangs on boot (maybe because a physical ascent device is
> used by network subsystem)
> 
> physical switch is OFF
> rfkill state is OFF
> => Activate interface in Gnome Connection Manager => System hang
> 
> test setup:
> Dell Vostro 3300
> Broadcom 4313 Wifi
> Kernel 3.5.[0-2] & 3.6
> Fedora 17


What Matthew wrote to me:
> > With the old dell-laptop code included everything was fine with
> > brcmsmac. So either generic platform code does not handle the switch
> > correct or there is no handling at all?
> 
> brcmsmac is broken. I suspect it was happily claiming to be
> unblocked, 
> but was ignored because dell-laptop claimed to be blocked.

Full discussion thread:
https://lkml.org/lkml/2012/8/23/234



             reply	other threads:[~2012-08-24  8:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24  8:51 Sebastian Poehn [this message]
2012-08-24 10:59 ` [BUG] brcmsmac: Invalid killswitch handling Arend van Spriel
2012-08-24 17:39   ` Sebastian Poehn

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=1345798314.1478.12.camel@localhost.localdomain \
    --to=sebastian.poehn@googlemail.com \
    --cc=brcm80211-dev-list@broadcom.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;
as well as URLs for NNTP newsgroup(s).