You are not logged in.

#1 2019-07-21 14:30:09

Nipsky
Member
From: Germany
Registered: 2011-10-03
Posts: 26

Wifi connection becoming unstable every view hours (Intel 7260)

Hi, my Wifi connection is becoming unstable every hours, connection is lost and built up multiple times. Sometimes it stabilizes again after a while, sometimes I have reload the driver and/or restart iwd, sometimes only a reboot helps. I already tried to switch from wpa_supplicant to iwd and from NetworkManager to connman, and I also disabled dhcpcd but the problem persists. I also played around with some driver options (like mentioned in this post: https://forum.manjaro.org/t/sovled-iwlw … m/82689/5)

Here is are dmesg messges from when the instability occurs:

[126414.297278] iwlwifi 0000:02:00.0: No beacon heard and the time event is over already...
[126414.297290] wlan2: Connection to AP 9c:c7:a6:4e:6e:14 lost
[126414.399170] wlan2: authenticate with 9c:c7:a6:4e:6e:14
[126414.401158] wlan2: send auth to 9c:c7:a6:4e:6e:14 (try 1/3)
[126414.426423] wlan2: authenticated
[126414.428919] wlan2: associate with 9c:c7:a6:4e:6e:14 (try 1/3)
[126414.434479] wlan2: RX AssocResp from 9c:c7:a6:4e:6e:14 (capab=0x431 status=0 aid=2)
[126414.447796] wlan2: associated
[126449.733151] wlan2: Connection to AP 9c:c7:a6:4e:6e:14 lost
[126449.816380] wlan2: authenticate with 9c:c7:a6:4e:6e:14
[126449.818343] wlan2: send auth to 9c:c7:a6:4e:6e:14 (try 1/3)
[126449.836001] wlan2: authenticated
[126449.838494] wlan2: associate with 9c:c7:a6:4e:6e:14 (try 1/3)
[126449.849714] wlan2: RX AssocResp from 9c:c7:a6:4e:6e:14 (capab=0x431 status=0 aid=2)
[126449.859874] wlan2: associated

Here are the iwd journal messages:

Jul 21 15:47:55 archpad iwd[30388]: authentication timed out
Jul 21 15:49:51 archpad iwd[30388]: Removing scan context for ifindex: 15
Jul 21 15:49:54 archpad iwd[30388]: Wiphy: 3, Name: phy3
Jul 21 15:49:54 archpad iwd[30388]:         Bands: 2.4 GHz 5 GHz
Jul 21 15:49:54 archpad iwd[30388]:         Ciphers: CCMP TKIP BIP
Jul 21 15:49:54 archpad iwd[30388]:         Supported iftypes: ad-hoc station ap p2p-client p2p-go p2p-device
Jul 21 15:49:54 archpad iwd[30388]: No ControlPortOverNL80211 setting, defaulting to True
Jul 21 16:00:55 archpad iwd[30388]: Received Deauthentication event, reason: 4, from_ap: false
Jul 21 16:00:58 archpad iwd[30388]: Received Deauthentication event, reason: 4, from_ap: false
Jul 21 16:00:58 archpad iwd[30388]: authentication timed out

And here are the connman journal messages:

Jul 21 16:00:55 archpad connmand[858]: wlan3 {TX} 12213 packets 2347052 bytes
Jul 21 16:00:55 archpad connmand[858]: wlan3 {update} flags 69699 <UP,RUNNING,LOWER_UP>
Jul 21 16:00:55 archpad connmand[858]: wlan3 {newlink} index 17 address 28:B2:BD:3C:50:4B mtu 1500
Jul 21 16:00:55 archpad connmand[858]: wlan3 {newlink} index 17 operstate 6 <UP>
Jul 21 16:00:58 archpad connmand[858]: wlan3 {RX} 10284 packets 7372991 bytes
Jul 21 16:00:58 archpad connmand[858]: wlan3 {TX} 12229 packets 2349682 bytes
Jul 21 16:00:58 archpad connmand[858]: wlan3 {update} flags 4099 <UP>
Jul 21 16:00:58 archpad connmand[858]: wlan3 {newlink} index 17 address 28:B2:BD:3C:50:4B mtu 1500
Jul 21 16:00:58 archpad connmand[858]: wlan3 {newlink} index 17 operstate 2 <DOWN>
Jul 21 16:00:58 archpad connmand[858]: wlan3 {del} route fe80:: gw :: scope 0 <UNIVERSE>

Is there anything I’m overlooking?

Offline

#2 2019-07-21 14:48:32

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,739

Re: Wifi connection becoming unstable every view hours (Intel 7260)

I note that it changed from wlan2 to wlan3.   Almost like it fell of the bus, reappeared, and was instantiated anew by the kernel.  What is the output of ip link  ?   And, is there any possibility there are multiple WiFi NICs?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2019-07-23 08:52:07

Nipsky
Member
From: Germany
Registered: 2011-10-03
Posts: 26

Re: Wifi connection becoming unstable every view hours (Intel 7260)

Hi, thanks for your reply. The enumeration could be cause by me reloading the driver (and seems I took the connman journal message after another reload). Still weird, could it be the kernel wasn’t releasing the module correctly? A short a while after my last post, I had to reboot because the module got “jammed” and I couldn’t reload it anymore. Anyway, seems more and more I actually don’t have to reload the module, I just need to wait for a while after the wifi breakdown until I can try to reconnect.

Still, is there a way to get more output out of iwlwifi? All I see in dmesg is this “No beacon heard and the time event is over already...” error when the wifi breaks.

By the way, ip link normally looks like this, I only have a single WiFi NIC:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s25: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 54:ee:75:25:5c:c5 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 28:b2:bd:3c:50:4b brd ff:ff:ff:ff:ff:ff

Offline

#4 2019-07-24 17:57:17

liara
Member
Registered: 2013-04-10
Posts: 32

Re: Wifi connection becoming unstable every view hours (Intel 7260)

Same here, Intel 7260, wpa_supplicant, netctl. Have you tried the lts kernel? For me it works fine, haven't yet tested with the latest lts 4.19.60 though. But that's not the solution. For me it's been dropping for quite some time now, maybe even before the 5 kernel. Will post my logs when I'm at it.

Edit: dmesg and journalctl from 5.2.2.

dmesg
audit: type=1131 audit(1564092063.176:56): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=man-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
wlp7s0: authenticate with 64:6e:ea:0e:22:f4
wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: authenticated
wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
wlp7s0: associated
wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
wlp7s0: authenticate with 64:6e:ea:0e:22:f4
wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: authenticated
wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
wlp7s0: associated
wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
wlp7s0: authenticate with 64:6e:ea:0e:22:f4
wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: authenticated
wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
wlp7s0: associated
wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
wlp7s0: authenticate with 64:6e:ea:0e:22:f4
wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: authenticated
wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
wlp7s0: associated
wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
wlp7s0: authenticate with 64:6e:ea:0e:22:f4
wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: authenticated
wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
wlp7s0: associated
wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
wlp7s0: authenticate with 64:6e:ea:0e:22:f4
wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: authenticated
wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
wlp7s0: associated
wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
wlp7s0: authenticate with 64:6e:ea:0e:22:f4
wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: authenticated
wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
wlp7s0: associated
wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
wlp7s0: authenticate with 64:6e:ea:0e:22:f4
wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: authenticated
wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
wlp7s0: associated
iwlwifi 0000:07:00.0: No beacon heard and the time event is over already...
wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
wlp7s0: authenticate with 64:6e:ea:0e:22:f4
wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: authenticated
wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
journalctl
Jul 26 00:01:03 stosd kernel: audit: type=1131 audit(1564092063.176:56): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=man-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 26 06:07:32 stosd systemd-udevd[3910]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jul 26 07:07:52 stosd kernel: wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
Jul 26 07:07:52 stosd dhcpcd[5225]: sending signal TERM to pid 722
Jul 26 07:07:52 stosd dhcpcd[5225]: waiting for pid 722 to exit
Jul 26 07:07:52 stosd dhcpcd[722]: received SIGTERM, stopping
Jul 26 07:07:52 stosd dhcpcd[722]: wlp7s0: removing interface
Jul 26 07:07:52 stosd dhcpcd[722]: dhcpcd exited
Jul 26 07:07:53 stosd kernel: wlp7s0: authenticate with 64:6e:ea:0e:22:f4
Jul 26 07:07:53 stosd kernel: wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:07:53 stosd kernel: wlp7s0: authenticated
Jul 26 07:07:53 stosd kernel: wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:07:53 stosd kernel: wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
Jul 26 07:07:53 stosd kernel: wlp7s0: associated
Jul 26 07:07:53 stosd dhcpcd[5237]: DUID 00:01:00:01:22:21:26:26:fc:f8:ae:81:77:95
Jul 26 07:07:53 stosd dhcpcd[5237]: wlp7s0: IAID ae:81:77:95
Jul 26 07:07:54 stosd dhcpcd[5237]: wlp7s0: rebinding lease of 192.168.0.100
Jul 26 07:07:54 stosd dhcpcd[5237]: wlp7s0: probing address 192.168.0.100/24
Jul 26 07:07:56 stosd kernel: wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
Jul 26 07:07:57 stosd kernel: wlp7s0: authenticate with 64:6e:ea:0e:22:f4
Jul 26 07:07:57 stosd kernel: wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:07:57 stosd kernel: wlp7s0: authenticated
Jul 26 07:07:57 stosd kernel: wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:07:57 stosd kernel: wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
Jul 26 07:07:57 stosd kernel: wlp7s0: associated
Jul 26 07:07:59 stosd kernel: wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
Jul 26 07:08:00 stosd dhcpcd[5237]: wlp7s0: leased 192.168.0.100 for 86400 seconds
Jul 26 07:08:00 stosd dhcpcd[5237]: wlp7s0: adding route to 192.168.64.0/24
Jul 26 07:08:00 stosd dhcpcd[5237]: wlp7s0: adding default route via 192.168.0.1
Jul 26 07:08:00 stosd dhcpcd[5237]: forked to background, child pid 5300
Jul 26 07:08:00 stosd dhcpcd[5311]: sending signal TERM to pid 5300
Jul 26 07:08:00 stosd dhcpcd[5311]: waiting for pid 5300 to exit
Jul 26 07:08:00 stosd dhcpcd[5300]: received SIGTERM, stopping
Jul 26 07:08:00 stosd dhcpcd[5300]: wlp7s0: removing interface
Jul 26 07:08:00 stosd dhcpcd[5300]: dhcpcd exited
Jul 26 07:08:00 stosd kernel: wlp7s0: authenticate with 64:6e:ea:0e:22:f4
Jul 26 07:08:00 stosd kernel: wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:08:00 stosd kernel: wlp7s0: authenticated
Jul 26 07:08:00 stosd kernel: wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:08:00 stosd kernel: wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
Jul 26 07:08:00 stosd kernel: wlp7s0: associated
Jul 26 07:08:00 stosd dhcpcd[5323]: DUID 00:01:00:01:22:21:26:26:fc:f8:ae:81:77:95
Jul 26 07:08:00 stosd dhcpcd[5323]: wlp7s0: IAID ae:81:77:95
Jul 26 07:08:00 stosd kernel: wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
Jul 26 07:08:00 stosd kernel: wlp7s0: authenticate with 64:6e:ea:0e:22:f4
Jul 26 07:08:00 stosd kernel: wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:08:00 stosd kernel: wlp7s0: authenticated
Jul 26 07:08:00 stosd kernel: wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:08:00 stosd kernel: wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
Jul 26 07:08:00 stosd kernel: wlp7s0: associated
Jul 26 07:08:00 stosd dhcpcd[5323]: wlp7s0: rebinding lease of 192.168.0.100
Jul 26 07:08:05 stosd kernel: wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
Jul 26 07:08:05 stosd dhcpcd[5323]: wlp7s0: DHCP lease expired
Jul 26 07:08:05 stosd dhcpcd[5323]: wlp7s0: soliciting a DHCP lease
Jul 26 07:08:06 stosd kernel: wlp7s0: authenticate with 64:6e:ea:0e:22:f4
Jul 26 07:08:06 stosd kernel: wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:08:06 stosd kernel: wlp7s0: authenticated
Jul 26 07:08:06 stosd kernel: wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:08:06 stosd kernel: wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
Jul 26 07:08:06 stosd kernel: wlp7s0: associated
Jul 26 07:08:06 stosd kernel: wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
Jul 26 07:08:06 stosd kernel: wlp7s0: authenticate with 64:6e:ea:0e:22:f4
Jul 26 07:08:06 stosd kernel: wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:08:06 stosd kernel: wlp7s0: authenticated
Jul 26 07:08:06 stosd kernel: wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:08:06 stosd kernel: wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
Jul 26 07:08:06 stosd kernel: wlp7s0: associated
Jul 26 07:08:08 stosd kernel: wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
Jul 26 07:08:09 stosd kernel: wlp7s0: authenticate with 64:6e:ea:0e:22:f4
Jul 26 07:08:09 stosd kernel: wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:08:09 stosd kernel: wlp7s0: authenticated
Jul 26 07:08:09 stosd kernel: wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:08:09 stosd kernel: wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
Jul 26 07:08:09 stosd kernel: wlp7s0: associated
Jul 26 07:08:17 stosd kernel: wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
Jul 26 07:08:18 stosd kernel: wlp7s0: authenticate with 64:6e:ea:0e:22:f4
Jul 26 07:08:18 stosd kernel: wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:08:18 stosd kernel: wlp7s0: authenticated
Jul 26 07:08:18 stosd kernel: wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:08:18 stosd kernel: wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
Jul 26 07:08:18 stosd kernel: wlp7s0: associated
Jul 26 07:08:18 stosd kernel: iwlwifi 0000:07:00.0: No beacon heard and the time event is over already...
Jul 26 07:08:18 stosd kernel: wlp7s0: Connection to AP 64:6e:ea:0e:22:f4 lost
Jul 26 07:08:19 stosd kernel: wlp7s0: authenticate with 64:6e:ea:0e:22:f4
Jul 26 07:08:19 stosd kernel: wlp7s0: send auth to 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:08:19 stosd kernel: wlp7s0: authenticated
Jul 26 07:08:19 stosd kernel: wlp7s0: associate with 64:6e:ea:0e:22:f4 (try 1/3)
Jul 26 07:08:19 stosd kernel: wlp7s0: RX AssocResp from 64:6e:ea:0e:22:f4 (capab=0x411 status=0 aid=2)
Jul 26 07:08:19 stosd kernel: wlp7s0: associated
Jul 26 07:08:40 stosd dhcpcd[5323]: timed out
Jul 26 07:08:40 stosd dhcpcd[5323]: dhcpcd exited
Jul 26 07:08:40 stosd dhcpcd[5633]: DUID 00:01:00:01:22:21:26:26:fc:f8:ae:81:77:95
Jul 26 07:08:40 stosd dhcpcd[5633]: wlp7s0: IAID ae:81:77:95
Jul 26 07:08:40 stosd dhcpcd[5633]: wlp7s0: soliciting a DHCP lease
Jul 26 07:08:40 stosd dhcpcd[5633]: wlp7s0: offered 192.168.0.100 from 192.168.0.1
Jul 26 07:08:40 stosd dhcpcd[5633]: wlp7s0: probing address 192.168.0.100/24
Jul 26 07:08:45 stosd dhcpcd[5633]: wlp7s0: leased 192.168.0.100 for 86400 seconds
Jul 26 07:08:45 stosd dhcpcd[5633]: wlp7s0: adding route to 192.168.64.0/24
Jul 26 07:08:45 stosd dhcpcd[5633]: wlp7s0: adding default route via 192.168.0.1
Jul 26 07:08:45 stosd dhcpcd[5633]: forked to background, child pid 5695
Jul 26 07:08:45 stosd dhcpcd[5706]: sending signal TERM to pid 5695
Jul 26 07:08:45 stosd dhcpcd[5706]: waiting for pid 5695 to exit
Jul 26 07:08:45 stosd dhcpcd[5695]: received SIGTERM, stopping
Jul 26 07:08:45 stosd dhcpcd[5695]: wlp7s0: removing interface
Jul 26 07:08:45 stosd dhcpcd[5695]: dhcpcd exited
Jul 26 07:08:45 stosd dhcpcd[5718]: DUID 00:01:00:01:22:21:26:26:fc:f8:ae:81:77:95
Jul 26 07:08:45 stosd dhcpcd[5718]: wlp7s0: IAID ae:81:77:95
Jul 26 07:08:46 stosd dhcpcd[5718]: wlp7s0: rebinding lease of 192.168.0.100
Jul 26 07:08:46 stosd dhcpcd[5718]: wlp7s0: probing address 192.168.0.100/24
Jul 26 07:08:51 stosd dhcpcd[5718]: wlp7s0: leased 192.168.0.100 for 86400 seconds
Jul 26 07:08:51 stosd dhcpcd[5718]: wlp7s0: adding route to 192.168.64.0/24
Jul 26 07:08:51 stosd dhcpcd[5718]: wlp7s0: adding default route via 192.168.0.1
Jul 26 07:08:51 stosd dhcpcd[5718]: forked to background, child pid 5757
Jul 26 07:08:51 stosd dhcpcd[5768]: sending signal TERM to pid 5757
Jul 26 07:08:51 stosd dhcpcd[5768]: waiting for pid 5757 to exit
Jul 26 07:08:51 stosd dhcpcd[5757]: received SIGTERM, stopping
Jul 26 07:08:51 stosd dhcpcd[5757]: wlp7s0: removing interface
Jul 26 07:08:51 stosd dhcpcd[5757]: dhcpcd exited
Jul 26 07:08:51 stosd dhcpcd[5780]: DUID 00:01:00:01:22:21:26:26:fc:f8:ae:81:77:95
Jul 26 07:08:51 stosd dhcpcd[5780]: wlp7s0: IAID ae:81:77:95
Jul 26 07:08:52 stosd dhcpcd[5780]: wlp7s0: rebinding lease of 192.168.0.100
Jul 26 07:08:52 stosd dhcpcd[5780]: wlp7s0: probing address 192.168.0.100/24
Jul 26 07:08:57 stosd dhcpcd[5780]: wlp7s0: leased 192.168.0.100 for 86400 seconds
Jul 26 07:08:57 stosd dhcpcd[5780]: wlp7s0: adding route to 192.168.64.0/24
Jul 26 07:08:57 stosd dhcpcd[5780]: wlp7s0: adding default route via 192.168.0.1
Jul 26 07:08:57 stosd dhcpcd[5780]: forked to background, child pid 5823
Jul 26 07:08:57 stosd dhcpcd[5834]: sending signal TERM to pid 5823
Jul 26 07:08:57 stosd dhcpcd[5834]: waiting for pid 5823 to exit
Jul 26 07:08:57 stosd dhcpcd[5823]: received SIGTERM, stopping
Jul 26 07:08:57 stosd dhcpcd[5823]: wlp7s0: removing interface
Jul 26 07:08:57 stosd dhcpcd[5823]: dhcpcd exited
Jul 26 07:08:57 stosd dhcpcd[5846]: DUID 00:01:00:01:22:21:26:26:fc:f8:ae:81:77:95
Jul 26 07:08:57 stosd dhcpcd[5846]: wlp7s0: IAID ae:81:77:95
Jul 26 07:08:57 stosd dhcpcd[5846]: wlp7s0: rebinding lease of 192.168.0.100
Jul 26 07:08:57 stosd dhcpcd[5846]: wlp7s0: probing address 192.168.0.100/24
Jul 26 07:09:03 stosd dhcpcd[5846]: wlp7s0: leased 192.168.0.100 for 86400 seconds
Jul 26 07:09:03 stosd dhcpcd[5846]: wlp7s0: adding route to 192.168.64.0/24
Jul 26 07:09:03 stosd dhcpcd[5846]: wlp7s0: adding default route via 192.168.0.1
Jul 26 07:09:03 stosd dhcpcd[5846]: forked to background, child pid 5884
Jul 26 07:09:03 stosd dhcpcd[5895]: sending signal TERM to pid 5884
Jul 26 07:09:03 stosd dhcpcd[5895]: waiting for pid 5884 to exit
Jul 26 07:09:03 stosd dhcpcd[5884]: received SIGTERM, stopping
Jul 26 07:09:03 stosd dhcpcd[5884]: wlp7s0: removing interface
Jul 26 07:09:03 stosd dhcpcd[5884]: dhcpcd exited
Jul 26 07:09:03 stosd dhcpcd[5907]: DUID 00:01:00:01:22:21:26:26:fc:f8:ae:81:77:95
Jul 26 07:09:03 stosd dhcpcd[5907]: wlp7s0: IAID ae:81:77:95
Jul 26 07:09:04 stosd dhcpcd[5907]: wlp7s0: rebinding lease of 192.168.0.100
Jul 26 07:09:04 stosd dhcpcd[5907]: wlp7s0: probing address 192.168.0.100/24
Jul 26 07:09:09 stosd dhcpcd[5907]: wlp7s0: leased 192.168.0.100 for 86400 seconds
Jul 26 07:09:09 stosd dhcpcd[5907]: wlp7s0: adding route to 192.168.64.0/24
Jul 26 07:09:09 stosd dhcpcd[5907]: wlp7s0: adding default route via 192.168.0.1
Jul 26 07:09:09 stosd dhcpcd[5907]: forked to background, child pid 5963
Jul 26 07:09:09 stosd dhcpcd[5974]: sending signal TERM to pid 5963
Jul 26 07:09:09 stosd dhcpcd[5974]: waiting for pid 5963 to exit
Jul 26 07:09:09 stosd dhcpcd[5963]: received SIGTERM, stopping
Jul 26 07:09:09 stosd dhcpcd[5963]: wlp7s0: removing interface
Jul 26 07:09:09 stosd dhcpcd[5963]: dhcpcd exited
Jul 26 07:09:09 stosd dhcpcd[5996]: DUID 00:01:00:01:22:21:26:26:fc:f8:ae:81:77:95
Jul 26 07:09:09 stosd dhcpcd[5996]: wlp7s0: IAID ae:81:77:95
Jul 26 07:09:10 stosd dhcpcd[5996]: wlp7s0: rebinding lease of 192.168.0.100
Jul 26 07:09:10 stosd dhcpcd[5996]: wlp7s0: probing address 192.168.0.100/24
Jul 26 07:09:15 stosd dhcpcd[5996]: wlp7s0: leased 192.168.0.100 for 86400 seconds
Jul 26 07:09:15 stosd dhcpcd[5996]: wlp7s0: adding route to 192.168.64.0/24
Jul 26 07:09:15 stosd dhcpcd[5996]: wlp7s0: adding default route via 192.168.0.1
Jul 26 07:09:15 stosd dhcpcd[5996]: forked to background, child pid 6074
Jul 26 07:09:15 stosd dhcpcd[6085]: sending signal TERM to pid 6074
Jul 26 07:09:15 stosd dhcpcd[6085]: waiting for pid 6074 to exit
Jul 26 07:09:15 stosd dhcpcd[6074]: received SIGTERM, stopping
Jul 26 07:09:15 stosd dhcpcd[6074]: wlp7s0: removing interface
Jul 26 07:09:15 stosd dhcpcd[6074]: dhcpcd exited
Jul 26 07:09:15 stosd dhcpcd[6097]: DUID 00:01:00:01:22:21:26:26:fc:f8:ae:81:77:95
Jul 26 07:09:15 stosd dhcpcd[6097]: wlp7s0: IAID ae:81:77:95
Jul 26 07:09:16 stosd dhcpcd[6097]: wlp7s0: rebinding lease of 192.168.0.100
Jul 26 07:09:16 stosd dhcpcd[6097]: wlp7s0: probing address 192.168.0.100/24
Jul 26 07:09:21 stosd dhcpcd[6097]: wlp7s0: leased 192.168.0.100 for 86400 seconds
Jul 26 07:09:21 stosd dhcpcd[6097]: wlp7s0: adding route to 192.168.64.0/24
Jul 26 07:09:21 stosd dhcpcd[6097]: wlp7s0: adding default route via 192.168.0.1
Jul 26 07:09:21 stosd dhcpcd[6097]: forked to background, child pid 6141

Setting TimeoutDHCP=40 in netctl profile didn't help, neither did setting Power Management off.

Last edited by liara (2019-07-26 06:08:56)

Offline

#5 2019-07-26 19:38:49

Brocellous
Member
Registered: 2017-11-27
Posts: 134

Re: Wifi connection becoming unstable every view hours (Intel 7260)

Does your bug match the descriptions of the users here? https://bugzilla.kernel.org/show_bug.cgi?id=203709

@ewaller, I believe the bump in interface id is from iwd's phy behavior on restarting iwd https://iwd.wiki.kernel.org/interface_lifecycle

Last edited by Brocellous (2019-07-26 19:50:00)

Offline

#6 2019-07-26 19:57:22

Nipsky
Member
From: Germany
Registered: 2011-10-03
Posts: 26

Re: Wifi connection becoming unstable every view hours (Intel 7260)

Brocellous wrote:

Does your bug match the descriptions of the users here? https://bugzilla.kernel.org/show_bug.cgi?id=203709

Thanks for the link, this looks very similar to what I’m experiencing.

By the way, after the recent kernel and firmware update a few days ago, I haven’t run into any instabilities so far. Let’s see what the next days bring…

Edit: Scratch that…

Last edited by Nipsky (2019-07-27 11:38:36)

Offline

Board footer

Powered by FluxBB