linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	Intel Linux Wireless <linuxwifi@intel.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi - L1 Enabled - LTR Enabled loop
Date: Mon, 14 Dec 2015 00:04:04 +0100	[thread overview]
Message-ID: <566DF964.7050904@broadcom.com> (raw)
In-Reply-To: <1449876779.2324.16.camel@sipsolutions.net>

On 12/12/2015 12:32 AM, Johannes Berg wrote:
> On Fri, 2015-12-11 at 15:17 -0800, Luis R. Rodriguez wrote:
>>
>> I just tried a base config from opensuse, then localmodconfig, then
>> 'make xenconfig' (which I need) and that worked. I can't debug
>> further but I think this config might help debug this further:
>>
>> http://drvbp1.linux-foundation.org/~mcgrof/tmp/config-iwl-fail.txt
>>
>> So -- my new config works, but I have no idea what fixed it, a config
>> option obviously. Not sure what though.
>>
>
> Can you post the good one too?

I had the same issue occasionally when coming out of suspend. Running 
4.1 vanilla kernel with 3160 device. The issue also occurred more often 
with particular ucode version. Running iwlwifi-3160-10.ucode now and 
have not seen the issue pop up since.

Gr. AvS


  reply	other threads:[~2015-12-13 23:04 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 [this message]
2015-12-14  4:00       ` Grumbach, Emmanuel
2015-12-14  8:48         ` Johannes Berg
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=566DF964.7050904@broadcom.com \
    --to=arend@broadcom.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=johannes@sipsolutions.net \
    --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 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).