You are not logged in.

#1 2019-10-12 08:14:24

Kandwo
Member
Registered: 2019-10-11
Posts: 3

Frequent disconnects from WiFi on 5.3 kernel

Using the newest 5.3 kernel I get frequent disconnects from the Wifi in my house. This is not the case with the lts kernel. I'm using wifi-menu to connect to the network. I want to use the latest kernel, since the graphical performance seems to be much better with it.

Here is some information (I'll be happy to provide more, but don't know where to find more relevant data):

uname -a

Linux 5.3.5-arch1-1-ARCH #1 SMP PREEMPT Mon Oct 7 19:03:08 UTC 2019 x86_64 GNU/Linux

dmesg information:

[ 3579.386845] BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u16:0/3056
[ 3579.386868] caller is ieee80211_xmit_fast_finish+0x5a/0x1e0 [mac80211]
[ 3579.386870] CPU: 0 PID: 3056 Comm: kworker/u16:0 Tainted: G           OE     5.3.5-arch1-1-ARCH #1
[ 3579.386870] Hardware name: LENOVO 20378/Lenovo Y50-70, BIOS 9ECN43WW(V3.03) 08/12/2015
[ 3579.386895] Workqueue: phy0 ieee80211_beacon_connection_loss_work [mac80211]
[ 3579.386896] Call Trace:
[ 3579.386899]  dump_stack+0x5c/0x80
[ 3579.386902]  debug_smp_processor_id.cold+0x4e/0x53
[ 3579.386926]  ieee80211_xmit_fast_finish+0x5a/0x1e0 [mac80211]
[ 3579.386951]  ieee80211_tx_dequeue+0x472/0xb50 [mac80211]
[ 3579.386962]  iwl_mvm_mac_itxq_xmit+0x6f/0x100 [iwlmvm]
[ 3579.386988]  _ieee80211_wake_txqs+0x218/0x450 [mac80211]
[ 3579.387014]  ieee80211_wake_queues_by_reason+0x7a/0xd0 [mac80211]
[ 3579.387040]  ieee80211_set_disassoc+0x330/0x5f0 [mac80211]
[ 3579.387059]  ? cfg80211_unlink_bss+0x95/0xc0 [cfg80211]
[ 3579.387084]  __ieee80211_disconnect+0xa0/0x130 [mac80211]
[ 3579.387088]  process_one_work+0x1d1/0x3a0
[ 3579.387090]  worker_thread+0x4a/0x3d0
[ 3579.387092]  kthread+0xfb/0x130
[ 3579.387095]  ? process_one_work+0x3a0/0x3a0
[ 3579.387096]  ? kthread_park+0x80/0x80
[ 3579.387099]  ret_from_fork+0x35/0x40
[ 3579.387104] BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u16:0/3056
[ 3579.387127] caller is ieee80211_xmit_fast_finish+0x5a/0x1e0 [mac80211]
[ 3579.387128] CPU: 0 PID: 3056 Comm: kworker/u16:0 Tainted: G           OE     5.3.5-arch1-1-ARCH #1
[ 3579.387129] Hardware name: LENOVO 20378/Lenovo Y50-70, BIOS 9ECN43WW(V3.03) 08/12/2015
[ 3579.387154] Workqueue: phy0 ieee80211_beacon_connection_loss_work [mac80211]
[ 3579.387155] Call Trace:
[ 3579.387158]  dump_stack+0x5c/0x80
[ 3579.387161]  debug_smp_processor_id.cold+0x4e/0x53
[ 3579.387185]  ieee80211_xmit_fast_finish+0x5a/0x1e0 [mac80211]
[ 3579.387209]  ieee80211_tx_dequeue+0x472/0xb50 [mac80211]
[ 3579.387221]  iwl_mvm_mac_itxq_xmit+0x6f/0x100 [iwlmvm]
[ 3579.387246]  _ieee80211_wake_txqs+0x218/0x450 [mac80211]
[ 3579.387272]  ieee80211_wake_queues_by_reason+0x7a/0xd0 [mac80211]
[ 3579.387298]  ieee80211_set_disassoc+0x330/0x5f0 [mac80211]
[ 3579.387317]  ? cfg80211_unlink_bss+0x95/0xc0 [cfg80211]
[ 3579.387342]  __ieee80211_disconnect+0xa0/0x130 [mac80211]
[ 3579.387346]  process_one_work+0x1d1/0x3a0
[ 3579.387348]  worker_thread+0x4a/0x3d0
[ 3579.387350]  kthread+0xfb/0x130
[ 3579.387352]  ? process_one_work+0x3a0/0x3a0
[ 3579.387354]  ? kthread_park+0x80/0x80
[ 3579.387357]  ret_from_fork+0x35/0x40
[ 3581.394031] iwlwifi 0000:08:00.0: fail to flush all tx fifo queues Q 10
[ 3581.394103] iwlwifi 0000:08:00.0: Queue 10 is active on fifo 1 and stuck for 10000
ms. SW [156, 242] HW [156, 242] FH TRB=0x0c010a0a3
[ 3581.504297] wlp8s0: Connection to AP 00:00:00:00:00:00 lost

[ 3579.387128] CPU: 0 PID: 3056 Comm: kworker/u16:0 Tainted: G           OE     5.3.5-arch1-1-ARCH #1
[ 3579.387129] Hardware name: LENOVO 20378/Lenovo Y50-70, BIOS 9ECN43WW(V3.03) 08/12/2015
[ 3579.387154] Workqueue: phy0 ieee80211_beacon_connection_loss_work [mac80211]
[ 3579.387155] Call Trace:
[ 3579.387158]  dump_stack+0x5c/0x80
[ 3579.387161]  debug_smp_processor_id.cold+0x4e/0x53
[ 3579.387185]  ieee80211_xmit_fast_finish+0x5a/0x1e0 [mac80211]
[ 3579.387209]  ieee80211_tx_dequeue+0x472/0xb50 [mac80211]
[ 3579.387221]  iwl_mvm_mac_itxq_xmit+0x6f/0x100 [iwlmvm]
[ 3579.387246]  _ieee80211_wake_txqs+0x218/0x450 [mac80211]
[ 3579.387272]  ieee80211_wake_queues_by_reason+0x7a/0xd0 [mac80211]
[ 3579.387298]  ieee80211_set_disassoc+0x330/0x5f0 [mac80211]
[ 3579.387317]  ? cfg80211_unlink_bss+0x95/0xc0 [cfg80211]
[ 3579.387342]  __ieee80211_disconnect+0xa0/0x130 [mac80211]
[ 3579.387346]  process_one_work+0x1d1/0x3a0
[ 3579.387348]  worker_thread+0x4a/0x3d0
[ 3579.387350]  kthread+0xfb/0x130
[ 3579.387352]  ? process_one_work+0x3a0/0x3a0
[ 3579.387354]  ? kthread_park+0x80/0x80
[ 3579.387357]  ret_from_fork+0x35/0x40
[ 3581.394031] iwlwifi 0000:08:00.0: fail to flush all tx fifo queues Q 10
[ 3581.394103] iwlwifi 0000:08:00.0: Queue 10 is active on fifo 1 and stuck for 10000
ms. SW [156, 242] HW [156, 242] FH TRB=0x0c010a0a3
[ 3607.459856] wlp8s0: authenticated
[ 3607.462568] wlp8s0: associate with 7c:39:53:ce:af:0f (try 1/3)
[ 3607.467289] wlp8s0: RX AssocResp from 7c:39:53:ce:af:0f (capab=0x411 status=0 aid=1)
[ 3607.470397] wlp8s0: associated
[ 3608.077471] iwlwifi 0000:08:00.0: No beacon heard and the time event is over already...
[ 3608.077550] wlp8s0: Connection to AP 7c:39:53:ce:af:0f lost
[ 3631.735834] wlp8s0: authenticate with 7c:39:53:ce:af:0f
[ 3631.738181] wlp8s0: send auth to 7c:39:53:ce:af:0f (try 1/3)
[ 3631.740861] wlp8s0: authenticated
[ 3631.741208] wlp8s0: associate with 7c:39:53:ce:af:0f (try 1/3)
[ 3631.745299] wlp8s0: RX AssocResp from 7c:39:53:ce:af:0f (capab=0x411 status=0 aid=1)
[ 3631.751648] wlp8s0: associated
[ 3633.500315] wlp8s0: Connection to AP 7c:39:53:ce:af:0f lost
[ 3723.955633] wlp8s0: authenticate with 7c:39:53:ce:af:0f
[ 3723.957984] wlp8s0: send auth to 7c:39:53:ce:af:0f (try 1/3)
[ 3723.960538] wlp8s0: authenticated
[ 3723.962856] wlp8s0: associate with 7c:39:53:ce:af:0f (try 1/3)
[ 3723.970717] wlp8s0: RX AssocResp from 7c:39:53:ce:af:0f (capab=0x411 status=0 aid=1)
[ 3723.974353] wlp8s0: associated
[ 3724.572153] iwlwifi 0000:08:00.0: No beacon heard and the time event is over already...
[ 3724.572213] wlp8s0: Connection to AP 7c:39:53:ce:af:0f lost
[ 3728.125450] wlp8s0: authenticate with 7c:39:53:ce:af:0f
[ 3728.128179] wlp8s0: send auth to 7c:39:53:ce:af:0f (try 1/3)
[ 3728.131056] wlp8s0: authenticated
[ 3728.132651] wlp8s0: associate with 7c:39:53:ce:af:0f (try 1/3)
[ 3728.138072] wlp8s0: RX AssocResp from 7c:39:53:ce:af:0f (capab=0x411 status=0 aid=1)
[ 3728.146749] wlp8s0: associated
[ 3743.873769] wlp8s0: Connection to AP 7c:39:53:ce:af:0f lost

lspci -k

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
        Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller
        Kernel modules: ie31200_edac
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
        Kernel driver in use: pcieport
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
        Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller
        Kernel driver in use: i915
        Kernel modules: i915
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
        Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
        Subsystem: Lenovo 8 Series/C220 Series Chipset Family USB xHCI
        Kernel driver in use: xhci_hcd
 Kernel modules: xhci_pci
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
        Subsystem: Lenovo 8 Series/C220 Series Chipset Family MEI Controller
        Kernel driver in use: mei_me
        Kernel modules: mei_me
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
        Subsystem: Lenovo 8 Series/C220 Series Chipset Family USB EHCI
        Kernel driver in use: ehci-pci
        Kernel modules: ehci_pci
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
        Subsystem: Lenovo 8 Series/C220 Series Chipset High Definition Audio Controller
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express
Root Port #1 (rev d5)
        Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express
Root Port #2 (rev d5)
        Kernel driver in use: pcieport
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express
Root Port #3 (rev d5)
        Kernel driver in use: pcieport
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express
Root Port #5 (rev d5)
        Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
        Subsystem: Lenovo 8 Series/C220 Series Chipset Family USB EHCI
        Kernel driver in use: ehci-pci
        Kernel modules: ehci_pci
00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
        Subsystem: Lenovo HM87 Express LPC Controller
        Kernel driver in use: lpc_ich
        Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port
SATA Controller 1 [AHCI mode] (rev 05)
        Subsystem: Lenovo 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode]
        Kernel driver in use: ahci
        Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller
(rev 05)
        Subsystem: Lenovo 8 Series/C220 Series Chipset Family SMBus Controller
        Kernel driver in use: i801_smbus
        Kernel modules: i2c_i801
01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 860M] (rev ff)
        Kernel modules: nouveau, nvidia_drm, nvidia
08:00.0 Network controller: Intel Corporation Wireless 3160 (rev 93)
        Subsystem: Intel Corporation Dual Band Wireless AC 3160
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
        Subsystem: Lenovo RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
        Kernel driver in use: r8169
        Kernel modules: r8169
0a:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5249 PCI Express Card Reader (rev 01)
        Subsystem: Lenovo RTS5249 PCI Express Card Reader
        Kernel driver in use: rtsx_pci
        Kernel modules: rtsx_pci

Offline

#2 2019-10-12 14:32:40

seth
Member
Registered: 2012-09-03
Posts: 12,690

Re: Frequent disconnects from WiFi on 5.3 kernel

Offline

#3 2019-10-12 16:32:32

gatlinnewhouse
Member
Registered: 2017-11-30
Posts: 12
Website

Re: Frequent disconnects from WiFi on 5.3 kernel

Looks like they wrote a patch as well. Hopefully it merges into upstream soon, I am also having this problem Kandwo.

Offline

#4 2019-10-13 11:12:13

gatlinnewhouse
Member
Registered: 2017-11-30
Posts: 12
Website

Re: Frequent disconnects from WiFi on 5.3 kernel

https://patchwork.ozlabs.org/patch/1168628/

is the patch. I am going to patch a kernel and try using it.

Offline

#5 2019-10-13 12:04:40

gatlinnewhouse
Member
Registered: 2017-11-30
Posts: 12
Website

Re: Frequent disconnects from WiFi on 5.3 kernel

gatlinnewhouse wrote:

https://patchwork.ozlabs.org/patch/1168628/

is the patch. I am going to patch a kernel and try using it.

I am still getting disconnects when I patched linux-clear with this patch.

dmesg:

[   11.484786] wlp3s0: authenticate with 5c:35:3b:e2:5d:94
[   11.487194] wlp3s0: send auth to 5c:35:3b:e2:5d:94 (try 1/3)
[   11.489040] wlp3s0: authenticated
[   11.489830] wlp3s0: associate with 5c:35:3b:e2:5d:94 (try 1/3)
[   11.493726] wlp3s0: RX AssocResp from 5c:35:3b:e2:5d:94 (capab=0x411 status=0 aid=3)
[   11.498482] wlp3s0: associated
[   15.015266] audit: type=1131 audit(1570968208.881:45): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   15.120545] audit: type=1130 audit(1570968208.986:46): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clr-power comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   15.120549] audit: type=1131 audit(1570968208.986:47): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=clr-power comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   29.546514] audit: type=1130 audit(1570968223.412:48): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   34.373141] audit: type=1131 audit(1570968228.239:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   40.013829] audit: type=1131 audit(1570968233.880:50): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   54.734390] audit: type=1130 audit(1570968248.600:51): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   65.013323] audit: type=1131 audit(1570968258.879:52): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   71.475616] [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=192.168.1.86 DST=224.0.0.252 LEN=53 TOS=0x00 PREC=0x00 TTL=255 ID=55371 PROTO=UDP SPT=5355 DPT=5355 LEN=33 
[   71.597383] [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=192.168.1.86 DST=224.0.0.252 LEN=53 TOS=0x00 PREC=0x00 TTL=255 ID=55488 PROTO=UDP SPT=5355 DPT=5355 LEN=33 
[   71.847355] [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=192.168.1.86 DST=224.0.0.252 LEN=53 TOS=0x00 PREC=0x00 TTL=255 ID=55725 PROTO=UDP SPT=5355 DPT=5355 LEN=33 
[  134.813926] [UFW BLOCK] IN=wlp3s0 OUT= MAC=a0:88:69:39:aa:76:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55553 PROTO=2 
[  183.436971] audit: type=1130 audit(1570968377.303:53): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=hostsblock comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  183.436974] audit: type=1131 audit(1570968377.303:54): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=hostsblock comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  184.009515] audit: type=1130 audit(1570968377.875:55): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=man-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  184.009519] audit: type=1131 audit(1570968377.875: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'
[  191.256358] audit: type=1130 audit(1570968385.122:57): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=updatedb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  191.256361] audit: type=1131 audit(1570968385.122:58): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=updatedb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  260.092685] [UFW BLOCK] IN=wlp3s0 OUT= MAC=a0:88:69:39:aa:76:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55554 PROTO=2 
[  340.395638] calling  init_hfsplus_fs+0x0/0x6e [hfsplus] @ 3292
[  340.395680] initcall init_hfsplus_fs+0x0/0x6e [hfsplus] returned 0 after 32 usecs
[  467.247370] [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55555 PROTO=2 
[  557.769510] [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55556 PROTO=2 
[  634.286181] snd_hda_intel 0000:00:1b.0: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.
[  707.992641] [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55557 PROTO=2 
[  826.777438] [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55558 PROTO=2 
[  925.705869] audit: type=1130 audit(1570969119.572:59): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  925.705874] audit: type=1131 audit(1570969119.572:60): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1219.690058] [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55561 PROTO=2 
[ 1316.071300] snd_hda_intel 0000:00:1b.0: Unstable LPIB (2880 >= 576); disabling LPIB delay counting
[ 1318.908235] wlp3s0: Connection to AP 5c:35:3b:e2:5d:94 lost

uname -a:

Linux rhizome 5.3.6-2-clear #1 SMP Sun Oct 13 13:32:04 CEST 2019 x86_64 GNU/Linux

lspci -k:

00:00.0 Host bridge: Intel Corporation Crystal Well DRAM Controller (rev 08)
	Subsystem: CLEVO/KAPOK Computer Crystal Well DRAM Controller
00:02.0 VGA compatible controller: Intel Corporation Crystal Well Integrated Graphics Controller (rev 08)
	Subsystem: CLEVO/KAPOK Computer Crystal Well Integrated Graphics Controller
	Kernel driver in use: i915
00:03.0 Audio device: Intel Corporation Crystal Well HD Audio Controller (rev 08)
	Subsystem: CLEVO/KAPOK Computer Crystal Well HD Audio Controller
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
	Subsystem: CLEVO/KAPOK Computer 8 Series/C220 Series Chipset Family USB xHCI
	Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
	Subsystem: CLEVO/KAPOK Computer 8 Series/C220 Series Chipset Family MEI Controller
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 05)
	Subsystem: CLEVO/KAPOK Computer Ethernet Connection I217-V
	Kernel driver in use: e1000e
	Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
	Subsystem: CLEVO/KAPOK Computer 8 Series/C220 Series Chipset Family USB EHCI
	Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
	Subsystem: CLEVO/KAPOK Computer 8 Series/C220 Series Chipset High Definition Audio Controller
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
	Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5)
	Kernel driver in use: pcieport
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5)
	Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
	Subsystem: CLEVO/KAPOK Computer 8 Series/C220 Series Chipset Family USB EHCI
	Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
	Subsystem: CLEVO/KAPOK Computer HM87 Express LPC Controller
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
	Subsystem: CLEVO/KAPOK Computer 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode]
	Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
	Subsystem: CLEVO/KAPOK Computer 8 Series/C220 Series Chipset Family SMBus Controller
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)
	Subsystem: CLEVO/KAPOK Computer RTS5229 PCI Express Card Reader
	Kernel driver in use: rtsx_pci
03:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
	Subsystem: Intel Corporation Dual Band Wireless-AC 3160
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

grub cmdline:

GRUB_CMDLINE_LINUX_DEFAULT="quiet console=tty0 console=ttyS0,115200n8 
cryptomgr.notests initcall_debug intel_iommu=igfx_off kvm-intel.nested=1 no_timer_check 
noreplace-smp page_alloc.shuffle=1 rcu_nocbs=0-64 rcupdate.rcu_expedited=1 
rootfstype=ext4,btrfs,xfs tsc=reliable vt.global_cursor_default=0 loglevel=3 rd.systemd.show_status=false i915.modeset=1 i915.disable_power_well=0 
i915.enable_lvds_downclock=1 i915.enable_psr=1 i915.enable_rc6=7 i915.enable_semaphores=1 
i915.enable_fbc=1 i915.enable_fastboot=0 snd_hda_intel.power_save=1 iwldvm.force_cam=0 
iwlwifi.power_save=0 iwlwifi.d0i3_disable=0 iwlwifi.uapsd_disable=0 iwlwifi.swcrypto=0 
iwlwifi.bt_coex_active=0 iwlwifi.11n_disable=0 ipv6.disable=1 net.ipv4.tcp_ecn=2 
usbcore.autosuspend=5 rd.udev.log-priority=3 splash nowatchdog nmi_watchdog=0 
libahci.ignore_sss=1 threadirqs ec_sys.write_support=1 rw"

Update: Following the instructions here to debug, https://wiki.archlinux.org/index.php/Ne … ets_(WiFi), and hopefully fix the problem. I've set the BSSID for the network as suggested. If that does not work, then I'll use

journalctl -f

to hopefully dig up deeper information.

Update2: Still times out. Full journal -fl log is here: https://pastebin.com/uYfShPr1. I think the key lines are:

Oct 13 14:43:02 rhizome kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=a0:88:69:39:aa:76:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55571 PROTO=2 
Oct 13 14:45:07 rhizome kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=a0:88:69:39:aa:76:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55572 PROTO=2 
Oct 13 14:48:38 rhizome kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55573 PROTO=2 
Oct 13 14:50:38 rhizome kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55574 PROTO=2 
Oct 13 14:52:09 rhizome kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55575 PROTO=2 
Oct 13 14:54:09 rhizome kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55576 PROTO=2 
Oct 13 14:56:20 rhizome kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55577 PROTO=2 
Oct 13 14:58:26 rhizome kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55578 PROTO=2 
Oct 13 15:01:10 rhizome kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55579 PROTO=2 
Oct 13 15:02:41 rhizome kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:5c:35:3b:e2:5d:92:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=55580 PROTO=2 
Oct 13 15:03:17 rhizome smartd[760]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 66 to 67
Oct 13 15:03:37 rhizome systemd[989]: Started Modprobed-db.
Oct 13 15:03:37 rhizome systemd[989]: Starting Timed resync...
Oct 13 15:03:37 rhizome modprobed-db[9613]: sort: open failed: /home/deleuze/.config/modprobed.db: Permission denied
Oct 13 15:03:37 rhizome systemd[989]: modprobed-db.service: Main process exited, code=exited, status=1/FAILURE
Oct 13 15:03:37 rhizome systemd[989]: modprobed-db.service: Failed with result 'exit-code'.
Oct 13 15:03:38 rhizome profile-sync-daemon[9614]: firefox resync successful
Oct 13 15:03:38 rhizome systemd[989]: psd-resync.service: Succeeded.
Oct 13 15:03:38 rhizome systemd[989]: Started Timed resync.
Oct 13 15:04:18 rhizome kernel: wlp3s0: Connection to AP 5c:35:3b:e2:5d:94 lost
Oct 13 15:04:18 rhizome wpa_supplicant[991]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=5c:35:3b:e2:5d:94 reason=4 locally_generated=1
Oct 13 15:04:18 rhizome NetworkManager[802]: <warn>  [1570971858.1104] sup-iface[0x558dce3e1220,wlp3s0]: connection disconnected (reason -4)
Oct 13 15:04:18 rhizome wpa_supplicant[991]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/1
Oct 13 15:04:18 rhizome wpa_supplicant[991]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Oct 13 15:04:18 rhizome NetworkManager[802]: <info>  [1570971858.1455] device (wlp3s0): supplicant interface state: completed -> disconnected
Oct 13 15:04:18 rhizome NetworkManager[802]: <info>  [1570971858.1455] device (p2p-dev-wlp3s0): supplicant management interface state: completed -> disconnected
Oct 13 15:04:18 rhizome NetworkManager[802]: <info>  [1570971858.2155] device (wlp3s0): supplicant interface state: disconnected -> scanning
Oct 13 15:04:18 rhizome NetworkManager[802]: <info>  [1570971858.2155] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> scanning
Oct 13 15:04:33 rhizome NetworkManager[802]: <warn>  [1570971873.8721] device (wlp3s0): link timed out.
Oct 13 15:04:33 rhizome NetworkManager[802]: <info>  [1570971873.8730] device (wlp3s0): state change: activated -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Oct 13 15:04:33 rhizome NetworkManager[802]: <info>  [1570971873.8737] manager: NetworkManager state is now DISCONNECTED

Last edited by gatlinnewhouse (2019-10-13 13:10:01)

Offline

#6 2019-10-13 12:52:36

seth
Member
Registered: 2012-09-03
Posts: 12,690

Re: Frequent disconnects from WiFi on 5.3 kernel

Please post a complete journal for a boot w/ the patched kernel.

Offline

#7 2019-10-13 13:14:55

gatlinnewhouse
Member
Registered: 2017-11-30
Posts: 12
Website

Re: Frequent disconnects from WiFi on 5.3 kernel

seth wrote:

Please post a complete journal for a boot w/ the patched kernel.

here it is https://gist.github.com/634dcb47c92a933 … daf216b233

Update: according to nm-applet, the network had both 5ghz and 2.4ghz bands, so I've selected the 5ghz. I know that sometimes problems can occur when the bands share the same SSID. Nevermind, it appears that this ap only has 2.4ghz...

Last edited by gatlinnewhouse (2019-10-13 13:33:07)

Offline

#8 2019-10-13 14:34:35

seth
Member
Registered: 2012-09-03
Posts: 12,690

Re: Frequent disconnects from WiFi on 5.3 kernel

Oct 13 14:03:16 rhizome systemd-journald[421]: Missed 572 kernel messages
sudo journalctl -b

However the crashes are gone, but you seem to be disconnected after ~20m and finally after ~5m, one disconnect is by local choice, in all other cases the  connection was lost.

I'd first cut out NM (stop, maybe disable it) and connect w/ wifi-menu to see whether this is due to NMs multiple accesses to the NIC (for pointless scanning)

When you're connected (no matter how) dump the output of "iw dev wlp3s0 link" - maybe the signal is just weak?
Also check the router log and notably lease times.

Offline

#9 2019-10-13 19:28:55

gatlinnewhouse
Member
Registered: 2017-11-30
Posts: 12
Website

Re: Frequent disconnects from WiFi on 5.3 kernel

seth wrote:

When you're connected (no matter how) dump the output of "iw dev wlp3s0 link" - maybe the signal is just weak?

Here it is with NM:

➜ iw dev wlp3s0 link
Connected to 5c:35:3b:e2:5d:94 (on wlp3s0)
	SSID: ONO54D5
	freq: 2412
	RX: 11518652 bytes (9929 packets)
	TX: 646942 bytes (4946 packets)
	signal: -57 dBm
	rx bitrate: 72.2 MBit/s MCS 7 short GI
	tx bitrate: 65.0 MBit/s MCS 6 short GI

	bss flags:	short-slot-time
	dtim period:	1
	beacon int:	100
seth wrote:

I'd first cut out NM (stop, maybe disable it) and connect w/ wifi-menu to see whether this is due to NMs multiple accesses to the NIC (for pointless scanning)

What package is wifi-menu with? I can't find it. Ty for the help btw smile

Update: nvm, found it https://wiki.archlinux.org/index.php/Netctl

Last edited by gatlinnewhouse (2019-10-13 19:29:59)

Offline

#10 2019-10-13 20:25:57

gatlinnewhouse
Member
Registered: 2017-11-30
Posts: 12
Website

Re: Frequent disconnects from WiFi on 5.3 kernel

Ok. I disable NM, I try to configure netctl. And each time I try to authenticate with the network, it fails. Maybe it's a weak signal.

Offline

#11 2019-10-13 20:26:48

seth
Member
Registered: 2012-09-03
Posts: 12,690

Re: Frequent disconnects from WiFi on 5.3 kernel

It fails how exactly? Error message?

Offline

#12 2019-10-13 20:43:33

gatlinnewhouse
Member
Registered: 2017-11-30
Posts: 12
Website

Re: Frequent disconnects from WiFi on 5.3 kernel

seth wrote:

It fails how exactly? Error message?

➜ systemctl status netctl@wlp3s0\\x2dONO54D5.service
● netctl@wlp3s0\x2dONO54D5.service - Networking for netctl profile wlp3s0-ONO54D5
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sun 2019-10-13 22:41:33 CEST; 3s ago
     Docs: man:netctl.profile(5)
  Process: 4540 ExecStart=/usr/lib/netctl/network start wlp3s0-ONO54D5 (code=exited, status=1/FAILURE)
 Main PID: 4540 (code=exited, status=1/FAILURE)

Oct 13 22:41:17 rhizome systemd[1]: Starting Networking for netctl profile wlp3s0-ONO54D5...
Oct 13 22:41:17 rhizome network[4540]: Starting network profile 'wlp3s0-ONO54D5'...
Oct 13 22:41:33 rhizome network[4540]: WPA association/authentication failed for interface 'wlp3s0'
Oct 13 22:41:33 rhizome network[4540]: Failed to bring the network up for profile 'wlp3s0-ONO54D5'
Oct 13 22:41:33 rhizome systemd[1]: netctl@wlp3s0\x2dONO54D5.service: Main process exited, code=exited, status=1/FAI>
Oct 13 22:41:33 rhizome systemd[1]: netctl@wlp3s0\x2dONO54D5.service: Failed with result 'exit-code'.
Oct 13 22:41:33 rhizome systemd[1]: Failed to start Networking for netctl profile wlp3s0-ONO54D5.

and

➜ journalctl -xe
Oct 13 22:41:17 rhizome systemd[1]: Starting Networking for netctl profile wlp3s0-ONO54D5...
Oct 13 22:41:17 rhizome network[4540]: Starting network profile 'wlp3s0-ONO54D5'...
Oct 13 22:41:33 rhizome network[4540]: WPA association/authentication failed for interface 'wlp3s0'
Oct 13 22:41:33 rhizome network[4540]: Failed to bring the network up for profile 'wlp3s0-ONO54D5'
Oct 13 22:41:33 rhizome systemd[1]: netctl@wlp3s0\x2dONO54D5.service: Main process exited, code=exited, status=1/FAI>
Oct 13 22:41:33 rhizome systemd[1]: netctl@wlp3s0\x2dONO54D5.service: Failed with result 'exit-code'.
Oct 13 22:41:33 rhizome systemd[1]: Failed to start Networking for netctl profile wlp3s0-ONO54D5.

Oct 13 22:41:17 rhizome systemd[1]: Starting Networking for netctl profile wlp3s0-ONO54D5...
-- Subject: A start job for unit netctl@wlp3s0\x2dONO54D5.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit netctl@wlp3s0\x2dONO54D5.service has begun execution.
-- 
-- The job identifier is 1911.
Oct 13 22:41:17 rhizome network[4540]: Starting network profile 'wlp3s0-ONO54D5'...
Oct 13 22:41:21 rhizome kernel: wlp3s0: authenticate with 5c:35:3b:e2:5d:94
Oct 13 22:41:21 rhizome kernel: wlp3s0: send auth to 5c:35:3b:e2:5d:94 (try 1/3)
Oct 13 22:41:21 rhizome kernel: wlp3s0: authenticated
Oct 13 22:41:21 rhizome kernel: wlp3s0: associate with 5c:35:3b:e2:5d:94 (try 1/3)
Oct 13 22:41:21 rhizome kernel: wlp3s0: RX AssocResp from 5c:35:3b:e2:5d:94 (capab=0x411 status=0 aid=3)
Oct 13 22:41:21 rhizome kernel: wlp3s0: associated
Oct 13 22:41:21 rhizome kernel: wlp3s0: disassociated from 5c:35:3b:e2:5d:94 (Reason: 14=MIC_FAILURE)
Oct 13 22:41:33 rhizome network[4540]: WPA association/authentication failed for interface 'wlp3s0'
Oct 13 22:41:33 rhizome dhclient[3120]: receive_packet failed on wlp3s0: Network is down
Oct 13 22:41:33 rhizome network[4540]: Failed to bring the network up for profile 'wlp3s0-ONO54D5'
Oct 13 22:41:33 rhizome systemd[1]: netctl@wlp3s0\x2dONO54D5.service: Main process exited, code=exited, status=1/FAI>
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- An ExecStart= process belonging to unit netctl@wlp3s0\x2dONO54D5.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Oct 13 22:41:33 rhizome systemd[1]: netctl@wlp3s0\x2dONO54D5.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit netctl@wlp3s0\x2dONO54D5.service has entered the 'failed' state with result 'exit-code'.
Oct 13 22:41:33 rhizome systemd[1]: Failed to start Networking for netctl profile wlp3s0-ONO54D5.
-- Subject: A start job for unit netctl@wlp3s0\x2dONO54D5.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit netctl@wlp3s0\x2dONO54D5.service has finished with a failure.
-- 
-- The job identifier is 1911 and the job result is failed.

Offline

#13 2019-10-13 21:16:51

seth
Member
Registered: 2012-09-03
Posts: 12,690

Re: Frequent disconnects from WiFi on 5.3 kernel

Try passing "iwlwifi.swcrypto=1" to the kernel.

Does this only happen when running on battery?
This thread blames IPv6 (though that seems odd): https://forum.manjaro.org/t/solved-prob … ds/40699/2
https://wiki.archlinux.org/index.php/IPv6#Disable_IPv6

Do you have control over the router?

Offline

#14 2019-10-14 12:46:25

gatlinnewhouse
Member
Registered: 2017-11-30
Posts: 12
Website

Re: Frequent disconnects from WiFi on 5.3 kernel

seth wrote:

Try passing "iwlwifi.swcrypto=1" to the kernel.

Will do and I'll report back!

seth wrote:

Does this only happen when running on battery?
This thread blames IPv6 (though that seems odd): https://forum.manjaro.org/t/solved-prob … ds/40699/2
https://wiki.archlinux.org/index.php/IPv6#Disable_IPv6

All of these tests have been on AC. I have only had my laptop plugged in for this.

seth wrote:

Do you have control over the router?

Unfortunately no.

Offline

#15 2019-10-14 12:53:40

gatlinnewhouse
Member
Registered: 2017-11-30
Posts: 12
Website

Re: Frequent disconnects from WiFi on 5.3 kernel

Netctl failed as well.

➜ systemctl status netctl@wlp3s0\\x2dONO54D5.service
● netctl@wlp3s0\x2dONO54D5.service - Networking for netctl profile wlp3s0-ONO54D5
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2019-10-14 14:51:13 CEST; 11s ago
     Docs: man:netctl.profile(5)
  Process: 2636 ExecStart=/usr/lib/netctl/network start wlp3s0-ONO54D5 (code=exited, status=1/FAILURE)
 Main PID: 2636 (code=exited, status=1/FAILURE)

Oct 14 14:50:57 rhizome systemd[1]: Starting Networking for netctl profile wlp3s0-ONO54D5...
Oct 14 14:50:57 rhizome network[2636]: Starting network profile 'wlp3s0-ONO54D5'...
Oct 14 14:51:12 rhizome network[2636]: WPA association/authentication failed for interface 'wlp3s0'
Oct 14 14:51:13 rhizome network[2636]: Failed to bring the network up for profile 'wlp3s0-ONO54D5'
Oct 14 14:51:13 rhizome systemd[1]: netctl@wlp3s0\x2dONO54D5.service: Main process exited, code=exited, status=1/FAILURE
Oct 14 14:51:13 rhizome systemd[1]: netctl@wlp3s0\x2dONO54D5.service: Failed with result 'exit-code'.
Oct 14 14:51:13 rhizome systemd[1]: Failed to start Networking for netctl profile wlp3s0-ONO54D5.
➜ journalctl -xe
Oct 14 14:50:57 rhizome systemd[1]: Starting Networking for netctl profile wlp3s0-ONO54D5...
-- Subject: A start job for unit netctl@wlp3s0\x2dONO54D5.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit netctl@wlp3s0\x2dONO54D5.service has begun execution.
-- 
-- The job identifier is 1443.
Oct 14 14:50:57 rhizome network[2636]: Starting network profile 'wlp3s0-ONO54D5'...
Oct 14 14:51:00 rhizome kernel: wlp3s0: authenticate with 5c:35:3b:e2:5d:94
Oct 14 14:51:00 rhizome kernel: wlp3s0: send auth to 5c:35:3b:e2:5d:94 (try 1/3)
Oct 14 14:51:00 rhizome kernel: wlp3s0: authenticated
Oct 14 14:51:00 rhizome kernel: wlp3s0: associate with 5c:35:3b:e2:5d:94 (try 1/3)
Oct 14 14:51:00 rhizome kernel: wlp3s0: RX AssocResp from 5c:35:3b:e2:5d:94 (capab=0x411 status=0 aid=3)
Oct 14 14:51:00 rhizome kernel: wlp3s0: associated
Oct 14 14:51:00 rhizome kernel: wlp3s0: disassociated from 5c:35:3b:e2:5d:94 (Reason: 14=MIC_FAILURE)
Oct 14 14:51:12 rhizome network[2636]: WPA association/authentication failed for interface 'wlp3s0'
Oct 14 14:51:13 rhizome network[2636]: Failed to bring the network up for profile 'wlp3s0-ONO54D5'
Oct 14 14:51:13 rhizome systemd[1]: netctl@wlp3s0\x2dONO54D5.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- An ExecStart= process belonging to unit netctl@wlp3s0\x2dONO54D5.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Oct 14 14:51:13 rhizome systemd[1]: netctl@wlp3s0\x2dONO54D5.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit netctl@wlp3s0\x2dONO54D5.service has entered the 'failed' state with result 'exit-code'.
Oct 14 14:51:13 rhizome systemd[1]: Failed to start Networking for netctl profile wlp3s0-ONO54D5.
-- Subject: A start job for unit netctl@wlp3s0\x2dONO54D5.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit netctl@wlp3s0\x2dONO54D5.service has finished with a failure.
-- 
-- The job identifier is 1443 and the job result is failed.

Honestly thinking of switching to iwd or something else.

Last edited by gatlinnewhouse (2019-10-14 13:17:30)

Offline

#16 2019-10-14 13:19:31

gatlinnewhouse
Member
Registered: 2017-11-30
Posts: 12
Website

Re: Frequent disconnects from WiFi on 5.3 kernel

Ok. Did some googling and came across this https://superuser.com/questions/663335/ … linux-wifi

I put

iwlmvm.power_scheme=1

in my grub boot parameters. It does not make sense to change

iwlwifi.power_save=0

to

iwlwifi.power_save=true

since the wiki disagrees https://wiki.archlinux.org/index.php/Po … _(iwlwifi)

Offline

#17 2019-10-14 14:37:53

gatlinnewhouse
Member
Registered: 2017-11-30
Posts: 12
Website

Re: Frequent disconnects from WiFi on 5.3 kernel

Ok. I logged in to look at the log for the router and found this:

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=5c:35:3b:e2:5d:90;CMTS-MAC=14:30:04:c8:fb:f5;CM-QOS=1.1;CM-VER=3.0;

DHCP leases for 1 hour by default. Should that be longer?

Added my laptop to the static MAC address option

Last edited by gatlinnewhouse (2019-10-14 14:50:58)

Offline

#18 2019-10-15 15:21:15

gatlinnewhouse
Member
Registered: 2017-11-30
Posts: 12
Website

Re: Frequent disconnects from WiFi on 5.3 kernel

Okay. I have connman + iwd working.

I am going to perform some tests later.

➜ iw dev wlp3s0 link
Connected to 5c:35:3b:e2:5d:94 (on wlp3s0)
	SSID: ONO54D5
	freq: 2462
	RX: 430231 bytes (729 packets)
	TX: 96017 bytes (685 packets)
	signal: -54 dBm
	rx bitrate: 72.2 MBit/s MCS 7 short GI
	tx bitrate: 72.2 MBit/s MCS 7 short GI

	bss flags:	short-slot-time
	dtim period:	1
	beacon int:	100

Update: So, I played some CS:S to test the connection and I did not have a single issue with this setup. Hopefully the patch I compiled in my kernel is merged upstream. Thank you seth for all the help! smile

Last edited by gatlinnewhouse (2019-10-15 17:56:55)

Offline

Board footer

Powered by FluxBB