All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Dimov <dimovnike@gmail.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Emmanuel Grumbach <egrumbach@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: packet loss, disconnects and possible bug in iwlwifi
Date: Thu, 28 May 2015 03:50:35 +0300	[thread overview]
Message-ID: <5566665B.3060703@gmail.com> (raw)
In-Reply-To: <1432760563.15971.37.camel@redhat.com>

Hello,
Yes,I use 5Ghz and I'm aware of dynamic rate scaling (i monitored it
with iwconfig before). It's just no matter how I load it i never shows
speeds more than 520mbps (very rarely i get 600 but it doesn't last even
1 second). I load it with iperf and the max *real* speed I get is about
240mbps in TCP mode. Under Windows 7, I can see 866mbps when there is load.

Is there a reason why it avoids speeds bigger than 520mbps? Also is it
normal to get only half of the connection speed with iperf?
Regards,
Nick.

On 28.05.2015 00:02, Dan Williams wrote:
> On Wed, 2015-05-27 at 22:46 +0300, Nick Dimov wrote:
>> Hello everyone.
>> I updated the regulatory database from here
>> https://www.kernel.org/pub/software/network/wireless-regdb/ (just copied
>> the regulatory.bin and the public key) and the problem is gone! Thank to
>> all of you and especially to Emmanuel Grumbach for suggesting this.
>>
>> Now another question - how to make it connect at 866mbps or at least
>> something close to it? Any ideas?
> iwlwifi does dynamic rate scaling, so you'll almost never see 866mbps.
> When traffic is idle it drops back to 1mbit rates and then when traffic
> starts, scales up from there.  Also, I'm pretty sure you'll never get
> 866mbps in the 2.4GHz band due to lack of bandwidth there, you'll have
> to go 5GHz for that.
>
> Use "iw dev <ifname> link" to see the current rate.
>
> Dan
>
>> Thanks you,
>> Nick.
>>
>> On 27.05.2015 21:34, Emmanuel Grumbach wrote:
>>> On Wed, May 27, 2015 at 6:55 PM, Dan Williams <dcbw@redhat.com> wrote:
>>>> On Wed, 2015-05-27 at 02:44 +0300, Nick Dimov wrote:
>>>>> Hello,
>>>>> thank you for your response. I attach the full syslog since the last
>>>>> boot which contains some disconnects. I enabled debug mode for
>>>>> wpa_supplicant with -dd option (let me know if you need anything else).
>>>>>
>>>>> I also tried connecting directly, i.e. without NetworkManager but
>>>>> manually with wpa_supplicant and I still get disconnects, howvever
>>>>> wpa_supplicant gives different logs with different drivers. Please, see
>>>>> the file wifi.log (you can see there the driver i used in
>>>>> wpa_supplicant, that log doesn't have the debug activated but let me
>>>>> know if you need that too)
>>>> So if NM isn't involved in your later runs (and it's not, looking at the
>>>> logs), then I'm not sure what the issue could be except something in the
>>>> driver.
>>>>
>>>> mai 27 02:31:54 nick-G55VW wpa_supplicant[1565]: nl80211: Event message
>>>> available
>>>> mai 27 02:31:54 nick-G55VW wpa_supplicant[1565]: nl80211: Drv Event 20
>>>> (NL80211_CMD_DEL_STATION) received for wlan5
>>>> mai 27 02:31:54 nick-G55VW wpa_supplicant[1565]: nl80211: Delete station
>>>> d8:50:e6:da:1d:b4
>>>> mai 27 02:31:54 nick-G55VW kernel: wlan5: deauthenticating from
>>>> d8:50:e6:da:1d:b4 by local choice (Reason: 3=DEAUTH_LEAVING)
>>>>
>>>> I don't see anything interesting around those lines, so I guess its up
>>>> to Emmanuel now...  the tracing he requests would be good to get.
>>>>
>>> I suspect a regulatory problem. This is why I asked what was the
>>> channel used on 2.4GHz. On 5.2GHz we have seen bugs happening because
>>> of the regulatory database being ancient on Ubuntu. 2.4GHz should rule
>>> these problems out, unless we are talking about channel 12 and up or
>>> something like that.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


      reply	other threads:[~2015-05-28  0:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-23 10:28 packet loss, disconnects and possible bug in iwlwifi Nick Dimov
2015-05-25 11:33 ` Emmanuel Grumbach
2015-05-26 23:44   ` Nick Dimov
2015-05-27  0:27     ` Emmanuel Grumbach
2015-05-27  0:41       ` Nick Dimov
2015-05-27 11:33         ` Emmanuel Grumbach
2015-05-27 13:54     ` Dan Williams
2015-05-27 14:08       ` Dan Williams
2015-05-27 14:18         ` Nick Dimov
2015-05-27 15:55     ` Dan Williams
2015-05-27 18:34       ` Emmanuel Grumbach
2015-05-27 19:02         ` Nick Dimov
2015-05-27 19:18         ` Nick Dimov
2015-05-27 19:24         ` Nick Dimov
2015-05-27 19:46         ` Nick Dimov
2015-05-27 21:02           ` Dan Williams
2015-05-28  0:50             ` Nick Dimov [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=5566665B.3060703@gmail.com \
    --to=dimovnike@gmail.com \
    --cc=dcbw@redhat.com \
    --cc=egrumbach@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 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.