From: Johannes Berg <johannes@sipsolutions.net>
To: Colin Guthrie <gmane@colin.guthr.ie>
Cc: linux-wireless@vger.kernel.org,
Matthew Garrett <mjg59@srcf.ucam.org>,
platform-driver-x86@vger.kernel.org
Subject: Re: [Regression] Problem with rfkill on 2.6.38
Date: Mon, 09 May 2011 10:36:35 +0200 [thread overview]
Message-ID: <1304930195.3475.17.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <ip6j66$o5f$1@dough.gmane.org> (sfid-20110426_170016_050429_A6E2C01A)
Hi Colin,
[Matthew, everybody from the platform list, please see
http://mid.gmane.org/ip6j66$o5f$1@dough.gmane.org for the full email
thread]
Sorry, took me a while to get back to your email.
> wifi works fine generally, but after cycling RFKILL I have to reload the
> various modules before it works again.
> [root@jimmy ~]# rmmod dell_laptop
I'm pretty sure this one's at fault, see below.
> Turn back on:
>
> iwlagn 0000:0b:00.0: RF_KILL bit toggled to enable radio.
See, iwlwifi just reports this from the hw.
> usb 4-2: new full speed USB device using uhci_hcd and address 4
And your BT USB device shows up on the bus too. But then:
> iwlagn 0000:0b:00.0: RF_KILL bit toggled to disable radio.
> usb 4-2: USB disconnect, address 4
iwlwifi reports that it was killed, and your BT USB device disappears.
> I've been looking through the various commits that could come into play
> (although I am sure there are others):
All the commits you listed are related to iwlwifi only. However, we can
see that both wifi and BT are killed again. Therefore, iwlwifi can't be
at fault (its rfkill line is basically a GPIO input, it can't cause BT
to drop from the bus).
The consequence is that the fault must be with dell_laptop, the BIOS is
the only thing that can be causing both to be rf-killed. (I'd also
suspect rfkill, but it has no changes since 2.6.37)
johannes
next parent reply other threads:[~2011-05-09 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ip6j66$o5f$1@dough.gmane.org>
2011-05-09 8:36 ` Johannes Berg [this message]
2011-05-09 16:30 ` [Regression] Problem with rfkill on 2.6.38 Colin Guthrie
2011-05-09 17:09 ` Colin Guthrie
2011-05-09 17:11 ` Matthew Garrett
[not found] ` <20110509171144.GA7194-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2011-05-10 9:36 ` Colin Guthrie
[not found] ` <4DC9072D.4030103-D409yXkIzt2rnn0nCzrM/w@public.gmane.org>
2011-05-10 14:48 ` Keng-Yü Lin
[not found] ` <BANLkTinVwnSei_VobfKtgzrwSP+cJSvxaQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-10 15:12 ` Colin Guthrie
2011-06-24 10:54 ` Colin Guthrie
2011-06-24 12:29 ` Keng-Yü Lin
2011-06-24 13:23 ` 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=1304930195.3475.17.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=gmane@colin.guthr.ie \
--cc=linux-wireless@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@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