All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Volker Mische <volker.mische@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Problem with 40Mhz on 2.5GHz with Intel 8260
Date: Wed, 21 Sep 2016 09:54:42 +0300	[thread overview]
Message-ID: <CANUX_P1n3aVC=95q1=dJFU=7WYof=adm=P1anyhG0nnr9vKGKA@mail.gmail.com> (raw)
In-Reply-To: <79ad55e3-d7f7-0605-3499-a6b289dfb4f6@gmail.com>

> Hi,
>
> On 09/20/2016 08:22 AM, Volker Mische wrote:
>> On 09/20/2016 07:39 AM, Emmanuel Grumbach wrote:
>>> On Mon, Sep 19, 2016 at 5:00 PM, Volker Mische <volker.mische@gmail.com> wrote:
>>>> I'm having connectivity issues with an Intel 8260 on a 2.5GHz network
>>>> when using 40Mhz. I'm getting errors like
>>>>
>>>>     Queue 2 stuck for 10000 ms.
>>>>
>>>> I've upgrade my system to the firmware version 21 (21.373438.0) and
>>>> Kernel 4.8.0-rc6 in hope that it fixes the issue and to be able to debug
>>>> the problem.
>>>>
>>>> I then found the page about platform noise [1]. I don't have any issue
>>>> for several hours now (normally I was hitting the issue every few
>>>> minutes) as I've set the cfg80211_disable_40mhz_24ghz parameter.
>
>>> We tried a few times to debug those, but they take a very long time to debug
>>> since typically we need lots of reproductions and the firmware team
>>> doesn't always
>>> the time to look at the data immediately so in the end, the people who
>>> reported this
>>> originally went away.
>>> Note that 40MHz on 2.4GHz is not an optimal configuration in crowded
>>> environment,
>>> but if you live in a place where you are pretty much the only one using those
>>> frequencies, then, it can be beneficial.
>>
>> It's at home. I normally see only one other wifi (I need to check which
>> frequency that one is using).
>>
>>
>>> What you can try is to disable low power states (by using power_scheme
>>> in iwlmvm) and see if it helps.
>>
>> I will try that.
>
> I've set the iwlmvm power_scheme to 1 (and allowed the 40Mhz
> connection). First I thought it's good, but after a while the queue
> still got stuck. Especially after waking up from a suspend (not sure if
> that matters).

Ok - good to know.

>
> What are the next steps?

can you try to unplug the power cord? I had reports that said that
this can help. Again, just a debug step to give us a hint of what you
can be experiencing.
Besides this, we need to go for firmware debugging. But as I said,
don't expect this to be fast and easy. Please open a bug in
bugzilla.kernel.org. CC linuxwifi@intel.com and we will guide you
there on how to provide the information we need.

  reply	other threads:[~2016-09-21  6:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 14:00 Problem with 40Mhz on 2.5GHz with Intel 8260 Volker Mische
2016-09-20  5:39 ` Emmanuel Grumbach
2016-09-20  6:22   ` Volker Mische
2016-09-20 15:50     ` Volker Mische
2016-09-21  6:54       ` Emmanuel Grumbach [this message]
2016-09-21  7:01         ` Volker Mische
2016-09-21  7:20           ` Emmanuel Grumbach
2016-09-21 20:19             ` Volker Mische
2016-09-22  5:32               ` 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='CANUX_P1n3aVC=95q1=dJFU=7WYof=adm=P1anyhG0nnr9vKGKA@mail.gmail.com' \
    --to=egrumbach@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=volker.mische@gmail.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.