Bug 203709 - iwlwifi: 8260: frequently disconnects since Linux 5.1 "No beacon heard and the time event is over already" - WIFI-25906
Summary: iwlwifi: 8260: frequently disconnects since Linux 5.1 "No beacon heard and th...
Status: ASSIGNED
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Intel Linux Wireless
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-25 23:06 UTC by Denis Lisov
Modified: 2019-08-12 20:29 UTC (History)
6 users (show)

See Also:
Kernel Version: 5.1.5
Tree: Mainline
Regression: Yes


Attachments
concatenation of full dmesg and post-boot logs of kernel+NM+wpa_supplicant (377.13 KB, text/plain)
2019-05-25 23:06 UTC, Denis Lisov
Details
journal excerpt for intel 8265 NIC on iwd/networkd, iwlwifi debug=0x20 (37.00 KB, text/plain)
2019-07-26 19:24 UTC, Ronan Pigott
Details

Description Denis Lisov 2019-05-25 23:06:34 UTC
Created attachment 282941 [details]
concatenation of full dmesg and post-boot logs of kernel+NM+wpa_supplicant

Hardware: Thinkpad P50 with Intel Corporation Wireless 8260 [8086:24f3]
Software: Gentoo Linux with vanilla kernel, NetworkManager using wpa_supplicant

In Linux 5.0 the WiFi connection to my home network is rather stable. In Linux 5.1 (5.1.5 at the moment) it's unstable with the following symptoms.

Ping check to the router looks like this
64 bytes from 192.168.183.1: icmp_seq=54 ttl=64 time=5.81 ms
64 bytes from 192.168.183.1: icmp_seq=55 ttl=64 time=1.00 ms
64 bytes from 192.168.183.1: icmp_seq=56 ttl=64 time=1.17 ms
64 bytes from 192.168.183.1: icmp_seq=57 ttl=64 time=3.31 ms
From 192.168.183.5 icmp_seq=58 Destination Host Unreachable
From 192.168.183.5 icmp_seq=59 Destination Host Unreachable
From 192.168.183.5 icmp_seq=60 Destination Host Unreachable
From 192.168.183.5 icmp_seq=65 Destination Host Unreachable
From 192.168.183.5 icmp_seq=66 Destination Host Unreachable
From 192.168.183.5 icmp_seq=67 Destination Host Unreachable
From 192.168.183.5 icmp_seq=68 Destination Host Unreachable
From 192.168.183.5 icmp_seq=69 Destination Host Unreachable
From 192.168.183.5 icmp_seq=70 Destination Host Unreachable
64 bytes from 192.168.183.1: icmp_seq=78 ttl=64 time=1.07 ms
64 bytes from 192.168.183.1: icmp_seq=79 ttl=64 time=0.940 ms
64 bytes from 192.168.183.1: icmp_seq=80 ttl=64 time=0.951 ms
64 bytes from 192.168.183.1: icmp_seq=81 ttl=64 time=0.950 ms
64 bytes from 192.168.183.1: icmp_seq=82 ttl=64 time=1.17 ms
and so on, changing from ok to host unreachable a few times per minute.

The dmesg output looks like this (full log in attachment):
[  408.580520] wlp4s0: associated
[  420.822273] wlp4s0: Connection to AP ec:43:f6:07:90:84 lost
[  423.420415] wlp4s0: authenticate with ec:43:f6:07:90:84
[  423.431798] wlp4s0: send auth to ec:43:f6:07:90:84 (try 1/3)
[  423.436016] wlp4s0: authenticated
[  423.438864] wlp4s0: associate with ec:43:f6:07:90:84 (try 1/3)
[  423.542285] wlp4s0: associate with ec:43:f6:07:90:84 (try 2/3)
[  423.550083] wlp4s0: RX AssocResp from ec:43:f6:07:90:84 (capab=0xc11 status=0 aid=3)
[  423.552862] wlp4s0: associated
[  424.045586] iwlwifi 0000:04:00.0: No beacon heard and the time event is over already...
[  424.045622] wlp4s0: Connection to AP ec:43:f6:07:90:84 lost
[  425.178388] wlp4s0: authenticate with ec:43:f6:07:90:84
[  425.188576] wlp4s0: send auth to ec:43:f6:07:90:84 (try 1/3)
[  425.191274] wlp4s0: authenticated
[  425.192183] wlp4s0: associate with ec:43:f6:07:90:84 (try 1/3)
[  425.202483] wlp4s0: RX AssocResp from ec:43:f6:07:90:84 (capab=0xc11 status=0 aid=3)
[  425.206217] wlp4s0: associated
[  425.802779] iwlwifi 0000:04:00.0: No beacon heard and the time event is over already...
[  425.802814] wlp4s0: Connection to AP ec:43:f6:07:90:84 lost
[  427.060487] wlp4s0: authenticate with ec:43:f6:07:90:84
[  427.069870] wlp4s0: send auth to ec:43:f6:07:90:84 (try 1/3)
[  427.072586] wlp4s0: authenticated
[  427.078966] wlp4s0: associate with ec:43:f6:07:90:84 (try 1/3)
[  427.185781] wlp4s0: associate with ec:43:f6:07:90:84 (try 2/3)
[  427.222630] wlp4s0: RX AssocResp from ec:43:f6:07:90:84 (capab=0xc11 status=0 aid=3)
[  427.225860] wlp4s0: associated
[  427.683876] iwlwifi 0000:04:00.0: No beacon heard and the time event is over already...
[  427.683911] wlp4s0: Connection to AP ec:43:f6:07:90:84 lost
[  440.104459] wlp4s0: authenticate with ec:43:f6:07:90:84
[  440.112495] wlp4s0: send auth to ec:43:f6:07:90:84 (try 1/3)
[  440.116197] wlp4s0: authenticated
[  440.119343] wlp4s0: associate with ec:43:f6:07:90:84 (try 1/3)
[  440.124865] wlp4s0: RX AssocResp from ec:43:f6:07:90:84 (capab=0xc11 status=0 aid=3)
[  440.129543] wlp4s0: associated
[  440.750534] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[  452.055008] wlp4s0: Connection to AP ec:43:f6:07:90:84 lost

The corresponding part of NetworkManager logs is attached too.
Comment 1 Ronan Pigott 2019-07-26 19:24:22 UTC
Created attachment 283993 [details]
journal excerpt for intel 8265 NIC on iwd/networkd, iwlwifi debug=0x20
Comment 2 Ronan Pigott 2019-07-26 19:26:16 UTC
I am experiencing what seems to be the same issue on the intel 8265.

```
$ lspci -kvnn | sed -n '/Network/,/^$/ p'
02:00.0 Network controller [0280]: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
	Subsystem: Intel Corporation Dual Band Wireless-AC 8265 [8086:1010]
	Flags: bus master, fast devsel, latency 0, IRQ 141
	Memory at edc00000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: <access denied>
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
```
In my experience the interface can remain stable for a long time, but occasionally will disconnect and then struggles to reassociate/authenticate for a while before becoming stable again. It sometimes records the 'no beacon heard' message and always disconnects with reason 4, being inactivity.

I'm using a different network stack, so I'll leave journal excerpts in case the iwd logging is more helpful. I've got some debugging set for iwlwifi as I was trying to debug my issue.

$ printf %#x\n $(cat /sys/module/iwlwifi/parameters/debug)
0x20

$ journalctl --boot=517d350fbd224b28a65e491ff95036db _KERNEL_DEVICE=+pci:0000:02:00.0 + _SYSTEMD_UNIT={iwd,systemd-network}.service
(attached)
Comment 3 Ronan Pigott 2019-07-26 19:35:49 UTC
forgot to mention -- in my case,

$ uname -r
5.2.2-arch1-1-ARCH
Comment 4 bugzilla.kernel.org 2019-08-01 01:57:29 UTC
Can see this occuring Intel Corporation Wireless 7260 as well on `5.1.15-arch1-1-ARCH`.
Comment 5 kurmikon 2019-08-12 20:29:36 UTC
It's happening also on my Intel 3165, even on Linux 5.0.

Note You need to log in before you can comment on or make changes to this bug.