From: Johannes Berg <johannes@sipsolutions.net>
To: "Борислав Събев" <borislavsabev@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Intel Wireless 7260 - Possible bug within iwlwifi
Date: Fri, 27 Feb 2015 17:31:00 +0100 [thread overview]
Message-ID: <1425054660.1960.7.camel@sipsolutions.net> (raw)
In-Reply-To: <CA+uMeVcwpfOfQ=TnQA5omYga5Qu1bynNYz1gAQbcR4VqpFcXXg@mail.gmail.com> (sfid-20150227_171142_538428_5980AB84)
On Fri, 2015-02-27 at 18:11 +0200, Борислав Събев wrote:
> The problem is that If our WiFi goes down (or we need to restart the
> router) after the router is back up the connection could not be
> established again.
I'm not sure I understand - the below has nothing to do with the router?
> In the dmesg line: "[ 167.863245] iwlwifi 0000:02:00.0: RF_KILL bit
> toggled to disable radio." is produced when we try to stop/start
> the adapter via its hardware button or the button in NetworkManager.
That's pretty normal. Does it also show "to enable radio"? If you're
saying it just gets stuck in rfkill-disabled state then this is much
more likely a platform than iwlwifi issue, perhaps in the ACPI or other
platform rfkill drivers.
> Hope this helps to solve the issue for everyone.
> Again I have 4 machines with this issue so I can also test different
> stuff on Debian 8 Jessie & Ubuntu 14.04!
I have no idea what you'd want to test :)
johannes
next prev parent reply other threads:[~2015-02-27 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+uMeVeu0y892+HPCNK5zbuk48WTawaue9p5j690D9n77yzw1w@mail.gmail.com>
[not found] ` <CA+uMeVct4LSHw9HsxFm1DCdEPDr81_SpkHFeyQptd2eR1+1XSg@mail.gmail.com>
2015-02-27 16:11 ` Intel Wireless 7260 - Possible bug within iwlwifi Борислав Събев
2015-02-27 16:31 ` Johannes Berg [this message]
2015-02-28 19:19 ` Emmanuel Grumbach
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=1425054660.1960.7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=borislavsabev@gmail.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).