From: Johannes Berg <johannes@sipsolutions.net>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
Arend van Spriel <arend@broadcom.com>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
linuxwifi <linuxwifi@intel.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi - L1 Enabled - LTR Enabled loop
Date: Mon, 14 Dec 2015 09:48:32 +0100 [thread overview]
Message-ID: <1450082912.3871.2.camel@sipsolutions.net> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB32E919DE2@hasmsx107.ger.corp.intel.com>
On Mon, 2015-12-14 at 04:00 +0000, Grumbach, Emmanuel wrote:
>
> This is really weird. I don't see how that could be firmware related.
> BTW, -10.ucode is fairly old :) we have -16.ucode out there.
I guess the question is how we get into this situation to start with?
About the only thing I can imagine is that we fail somehow during
initialization (without printing any other message) and higher layers
like wpa_supplicant/network-manager/... simply try to bring up the
device over and over again?
johannes
next prev parent reply other threads:[~2015-12-14 8:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 18:59 iwlwifi - L1 Enabled - LTR Enabled loop Luis R. Rodriguez
2015-12-11 23:17 ` Luis R. Rodriguez
2015-12-11 23:32 ` Johannes Berg
2015-12-13 23:04 ` Arend van Spriel
2015-12-14 4:00 ` Grumbach, Emmanuel
2015-12-14 8:48 ` Johannes Berg [this message]
2015-12-16 7:52 ` 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=1450082912.3871.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=mcgrof@do-not-panic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.