Re: packet loss, disconnects and possible bug in iwlwifi

[Nick Dimov <dimovnike@gmail.com>]

Hello,
the channel for 2.4Ghz is:
Channel: 6
Frequency:2.437 GHz (Channel 6)
Quality=65/70  Signal level=-45 dBm 

Also I can't find how to activate CONFIG_IWLWIFI_TRACING in kernel (it's
missing in my kernel's config). I'm using the 3.19 kernel. The trace-cmd
seems to run, how can I check if it produces the trace you need?

Please, let me know!
Thanks.

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.