linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Stephen Kent <smkent@smkent.net>
Cc: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ilw@linux.intel.com" <ilw@linux.intel.com>
Subject: Re: [Ilw] RX laggy/choppy/stuck without TX on Intel Wireless 7260 with iwlwifi
Date: Mon, 24 Feb 2014 07:01:57 +0200	[thread overview]
Message-ID: <530AD245.7090204@gmail.com> (raw)
In-Reply-To: <CAC45b7mGq3ykRxXu2qAvJQ-PaWBzQpW5VhGg6hxCqiSS7umQrw@mail.gmail.com>



On 02/24/2014 06:19 AM, Stephen Kent wrote:
> On Sun, Feb 23, 2014 at 8:04 PM, Emmanuel Grumbach <egrumbach@gmail.com> wrote:
>>
>>
>>>>>
>>>>
>>>> Could you please try to reproduce with power save disabled?
>>>>
>>>> options iwlmvm power_scheme=1
>>>>
>>>> Thanks.
>>>
>>>
>>> Huh, interesting. When I set that option the problem seems to go away.
>>> I flipped back and forth between power_scheme=1 and power_scheme=2 in
>>> iwlmvm (modinfo says 2 is the default), and the problem didn't
>>> reproduce when power_scheme=1. I assume my battery life will suffer if
>>> I permanently set power_scheme=1? :-)
>>>
>>> Should I take a new trace or gather any other information?
>>
>> Not needed
>>
>>>
>>> I won't be my computer all day but I'll be able to respond / collect
>>> any needed info intermittently.
>>>
>>
>> I guess the best would be to upgrade to 3.13.5 with new firmware... Or to stay with power_scheme=1 in the meantime.
>>
>>
>>> Thanks,
>>>
>>> Stephen
>>>
> 
> 
> OK. Was this a bug that was identified and fixed between 3.11 and
> 3.13.5? I looked briefly at the kernel git log messages at
> https://github.com/torvalds/linux/commits/master/drivers/net/wireless/iwlwifi/mvm
> but I am completely unfamiliar with this code.

No - I can't think about any patch that could fix your issue. But 3.13 supports a newer firmware in which the power save code has been rewritten.

> 
> Until I upgrade, I'll just set power_scheme=1.
> 
> Thanks again for your help!
> 
> Stephen
> 

      reply	other threads:[~2014-02-24  5:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-22  5:00 RX laggy/choppy/stuck without TX on Intel Wireless 7260 with iwlwifi Stephen Kent
2014-02-23  6:18 ` [Ilw] " Grumbach, Emmanuel
2014-02-23  6:55   ` Stephen Kent
2014-02-23  7:02     ` Grumbach, Emmanuel
2014-02-23 20:02       ` Emmanuel Grumbach
2014-02-23 20:42         ` Stephen Kent
2014-02-24  4:04           ` Emmanuel Grumbach
2014-02-24  4:19             ` Stephen Kent
2014-02-24  5:01               ` Emmanuel Grumbach [this message]

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=530AD245.7090204@gmail.com \
    --to=egrumbach@gmail.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=ilw@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=smkent@smkent.net \
    /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).