You are not logged in.

#1 2020-04-06 13:11:05

snack
Member
From: Italy
Registered: 2009-01-13
Posts: 777

Wifi card looses network connection

I have a Dell XPS 15 9570, with a Killer 1535 wireless card:

$ lspci -vq
  . . . 
3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
        Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter
        Flags: bus master, fast devsel, latency 0, IRQ 149
        Memory at ed200000 (64-bit, non-prefetchable) [size=2M]
        Capabilities: <access denied>
        Kernel driver in use: ath10k_pci
        Kernel modules: ath10k_pci

After a variable amount of time, typically ranging from a half to two hours, the network partially stops to work. I cannot ping any address (not even the gateway) and I cannot browse any web page; curious enough, any already established connection like ssh sessions continue to work flawlessly. In this state I see no error neither in dmesg nor in ip addr or ip route: the wireless interface seems to be up and running, the ip address is set and also the routes. The only solution is to manually restart the network (I use ntectl-auto). This does not seem to be a router issue since every other device at home (4 Android + 1 Windows 10) work fine, so I guess the problem is my wireless card.

Now, the Killer card is quite notorious but mostly among Windows users. I didn't have any serious issue since recently but I used Wifi rarely (at work I use the laptop with an ethernet cable). Now that I'm forced at home and using wifi all day long I noticed this bad problem, but I can't really tell if it is a new issue and eventually when it started. It happens both with linux-ck-skylake and linux-lts. Searching on the internet I found this page on the Killer site where it is suggested to manually update the firmware: I don't know if it's a reasonable suggestion since I guess that firmware in Arch is already up-to-date.

Should I try updating anyway or is there anything else worth trying? Thanks.

Offline

#2 2020-04-06 13:18:08

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 9,710

Re: Wifi card looses network connection

That same exact chip works without issues here, as always post your journal log when the issue happens.

Offline

#3 2020-04-06 14:42:57

snack
Member
From: Italy
Registered: 2009-01-13
Posts: 777

Re: Wifi card looses network connection

@V1del: thanks for your reply. Here are some logs and info just after the network restart, when everything works:

# dmesg | tail
[ 5855.174791] wlan0: authenticate with a0:4f:d4:02:ba:b3
[ 5855.235292] wlan0: send auth to a0:4f:d4:02:ba:b3 (try 1/3)
[ 5855.238066] wlan0: authenticated
[ 5855.239089] wlan0: associate with a0:4f:d4:02:ba:b3 (try 1/3)
[ 5855.243631] wlan0: RX AssocResp from a0:4f:d4:02:ba:b3 (capab=0x411 status=0 aid=7)
[ 5855.245951] wlan0: associated
[ 5855.269794] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

# ip addr
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 9c:b6:d0:be:bd:8d brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.2/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
       valid_lft 21460sec preferred_lft 18760sec
    inet6 fe80::9eb6:d0ff:febe:bd8d/64 scope link 
       valid_lft forever preferred_lft forever
       
# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=6.95 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=6.55 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=8.94 ms
^C
--- 192.168.1.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 6.553/7.482/8.941/1.044 ms

And this is the same just after the problem appeared:

# dmesg | tail
[ 5855.174791] wlan0: authenticate with a0:4f:d4:02:ba:b3
[ 5855.235292] wlan0: send auth to a0:4f:d4:02:ba:b3 (try 1/3)
[ 5855.238066] wlan0: authenticated
[ 5855.239089] wlan0: associate with a0:4f:d4:02:ba:b3 (try 1/3)
[ 5855.243631] wlan0: RX AssocResp from a0:4f:d4:02:ba:b3 (capab=0x411 status=0 aid=7)
[ 5855.245951] wlan0: associated
[ 5855.269794] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 6610.874953] audit: type=1100 audit(1586180192.966:154): pid=8488 uid=10085 auid=10085 ses=2 msg='op=PAM:authentication grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=stryke addr=? terminal=pts/3 res=success'
[ 6610.875035] audit: type=1101 audit(1586180192.966:155): pid=8488 uid=10085 auid=10085 ses=2 msg='op=PAM:accounting grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=stryke addr=? terminal=pts/3 res=success'
[ 6610.875372] audit: type=1103 audit(1586180192.966:156): pid=8488 uid=10085 auid=10085 ses=2 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=stryke addr=? terminal=pts/3 res=success'
[ 6610.875435] audit: type=1105 audit(1586180192.966:157): pid=8488 uid=10085 auid=10085 ses=2 msg='op=PAM:session_open grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=stryke addr=? terminal=pts/3 res=success'
[ 7091.071804] audit: type=1106 audit(1586180673.154:158): pid=8488 uid=10085 auid=10085 ses=2 msg='op=PAM:session_close grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=stryke addr=? terminal=pts/3 res=success'
[ 7091.071828] audit: type=1104 audit(1586180673.154:159): pid=8488 uid=10085 auid=10085 ses=2 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=stryke addr=? terminal=pts/3 res=success'
[ 7101.844585] audit: type=1106 audit(1586180683.924:160): pid=889 uid=0 auid=10085 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="mori" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
[ 7101.844656] audit: type=1104 audit(1586180683.924:161): pid=889 uid=0 auid=10085 ses=2 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit acct="mori" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
[ 7105.818836] audit: type=1100 audit(1586180687.904:162): pid=9059 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
[ 7105.818871] audit: type=1101 audit(1586180687.904:163): pid=9059 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
[ 7105.819045] audit: type=1103 audit(1586180687.904:164): pid=9059 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
[ 7105.833042] audit: type=1130 audit(1586180687.914:165): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@975 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 7105.836533] audit: type=1101 audit(1586180687.924:166): pid=9062 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="sddm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 7105.836571] audit: type=1103 audit(1586180687.924:167): pid=9062 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="sddm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 7105.836631] audit: type=1006 audit(1586180687.924:168): pid=9062 uid=0 old-auid=4294967295 auid=975 tty=(none) old-ses=4294967295 ses=4 res=1
[ 7105.837044] audit: type=1105 audit(1586180687.924:169): pid=9062 uid=0 auid=975 ses=4 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sddm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 7111.889873] kauditd_printk_skb: 2 callbacks suppressed
[ 7111.889886] audit: type=1100 audit(1586180693.973:172): pid=9082 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_tally2,pam_shells,pam_unix,pam_permit acct="mori" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
[ 7111.894479] audit: type=1101 audit(1586180693.973:173): pid=9082 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="mori" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
[ 7111.894751] audit: type=1103 audit(1586180693.973:174): pid=9082 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit acct="mori" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
[ 7111.894922] audit: type=1006 audit(1586180693.973:175): pid=9082 uid=0 old-auid=4294967295 auid=10085 tty=(none) old-ses=4294967295 ses=5 res=1
[ 7111.902200] audit: type=1105 audit(1586180693.983:176): pid=9082 uid=0 auid=10085 ses=5 msg='op=PAM:session_open grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="mori" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
[ 7111.976234] audit: type=1106 audit(1586180694.063:177): pid=9059 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_unix,pam_systemd acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
[ 7111.976291] audit: type=1104 audit(1586180694.063:178): pid=9059 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0 res=success'
[ 7121.531537] audit: type=1100 audit(1586180703.613:179): pid=9518 uid=10085 auid=10085 ses=5 msg='op=PAM:authentication grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=stryke addr=? terminal=pts/1 res=success'
[ 7121.531575] audit: type=1101 audit(1586180703.613:180): pid=9518 uid=10085 auid=10085 ses=5 msg='op=PAM:accounting grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=stryke addr=? terminal=pts/1 res=success'
[ 7121.531846] audit: type=1103 audit(1586180703.613:181): pid=9518 uid=10085 auid=10085 ses=5 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=stryke addr=? terminal=pts/1 res=success'
[ 7121.531898] audit: type=1105 audit(1586180703.613:182): pid=9518 uid=10085 auid=10085 ses=5 msg='op=PAM:session_open grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=stryke addr=? terminal=pts/1 res=success'
[ 7122.083873] audit: type=1131 audit(1586180704.163:183): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@975 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 7122.091747] audit: type=1131 audit(1586180704.173:184): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@975 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'


# ip addr
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 9c:b6:d0:be:bd:8d brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.2/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
       valid_lft 17800sec preferred_lft 15100sec
    inet6 fe80::9eb6:d0ff:febe:bd8d/64 scope link 
       valid_lft forever preferred_lft forever

# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
^C
--- 192.168.1.1 ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6233ms

Nothing relevant (at least in my opinion) appears in dmesg after the initial connection to the access point; journalctl is spammed with a lot of Plasma/KDe/Qt logs but I checked it and it does not contain anything network-related: searching for "dhcpcd" and for "kernel: wlan0" shows nothing between the original connection to the network and the network restart after the problem appeared. Finally, ping is not able to reach the gateway. While my laptop was in the faulty network condition the router was fully working, as I checked with my phone.
Please tell me if I should provide some other log (I will do as soon as the proble reappears).

Offline

#4 2020-04-06 15:24:22

seth
Member
Registered: 2012-09-03
Posts: 14,795

Re: Wifi card looses network connection

Nothing relevant (at least in my opinion)

Because the random tail starts after the interesting action.

Please post the complete system journal, "sudo journalctl -b".

Offline

#5 2020-04-06 15:40:11

snack
Member
From: Italy
Registered: 2009-01-13
Posts: 777

Re: Wifi card looses network connection

@seth: thanks for your reply. Please download the journalctl log from here.

Offline

#6 2020-04-06 17:11:55

seth
Member
Registered: 2012-09-03
Posts: 14,795

Re: Wifi card looses network connection

So you did

apr 06 16:29:10 stryke sudo[12052]:     mori : TTY=pts/4 ; PWD=/home/mori ; USER=root ; COMMAND=/usr/bin/systemctl restart netctl-auto@wlan0
…
apr 06 17:36:27 stryke sudo[14797]:     mori : TTY=pts/6 ; PWD=/tmp ; USER=root ; COMMAND=/usr/bin/systemctl restart netctl-auto@wlan0

I assume somewhen during that time the condition manifested (causing the restarts)?
This

apr 06 16:51:57 stryke baloo_file_extractor[13192]: Qt: Session management error: Could not open network socket
apr 06 16:56:56 stryke kscreenlocker_greet[13316]: Qt: Session management error: networkIdsList argument is NULL

seems to indicate the earliest moment of network failure.

There's indeed no kernel or wpa or netctl related message that would indicate problems.

MTU mismatch? What's the output of

ip a; ip r

(in general and when thisngs fall apart)?

Also (though this should no longer be an issue)

sysctl net.ipv4.tcp_congestion_control

Offline

#7 2020-04-07 07:37:31

snack
Member
From: Italy
Registered: 2009-01-13
Posts: 777

Re: Wifi card looses network connection

Thanks seth for taking the time to look at the logs! Indeed the network restart were triggered by me to fix the issue after collecting the info (otherwise I would not have been able to upload them...).
Here are the additional info you requested. When the network is working:

$ ip r
default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.2 metric 302 
192.168.1.0/24 dev wlan0 proto dhcp scope link src 192.168.1.2 metric 302 

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 9c:b6:d0:be:bd:8d brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.2/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
       valid_lft 19663sec preferred_lft 16963sec
    inet6 fe80::9eb6:d0ff:febe:bd8d/64 scope link 
       valid_lft forever preferred_lft forever
3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 00:e0:4c:a2:02:4e brd ff:ff:ff:ff:ff:ff
    altname enp58s0u1u4
    
$ sysctl net.ipv4.tcp_congestion_control
net.ipv4.tcp_congestion_control = cubic

When the network stopped working:

$ ip r
default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.2 metric 302 
192.168.1.0/24 dev wlan0 proto dhcp scope link src 192.168.1.2 metric 302

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 9c:b6:d0:be:bd:8d brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.2/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
       valid_lft 18182sec preferred_lft 15482sec
    inet6 fe80::9eb6:d0ff:febe:bd8d/64 scope link 
       valid_lft forever preferred_lft forever
3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 00:e0:4c:a2:02:4e brd ff:ff:ff:ff:ff:ff
    altname enp58s0u1u4
    
$ sysctl net.ipv4.tcp_congestion_control
net.ipv4.tcp_congestion_control = cubic

Apart from the obviously different values of valid_lft and preferred_lft they seem completely identical to me.

Last edited by snack (2020-04-07 07:37:44)

Offline

#8 2020-04-08 06:59:01

seth
Member
Registered: 2012-09-03
Posts: 14,795

Re: Wifi card looses network connection

MTU and congestion are default, you retain carrier, IP and route, there're no errors from your kernel.

Try passing "ath10k_core.cryptmode=1" (use software encryption) to the kernel and see whether that has any impact.
If not, before enabling the ath10k debug output, I'd first take a look at the router log (if you have access)

Offline

#9 2020-04-08 13:45:06

snack
Member
From: Italy
Registered: 2009-01-13
Posts: 777

Re: Wifi card looses network connection

Hi seth, I'll try with cryptmode setting. I don't think that my router allows for seeing any log, it's a standard model provided by the ISP so very low level, but I'll give a look.

Offline

#10 2020-04-09 10:33:24

snack
Member
From: Italy
Registered: 2009-01-13
Posts: 777

Re: Wifi card looses network connection

Here is the log of the router (the MAC address of my machine is 9c:b6:d0:be:bd:8d):

[2020-04-09T11:38:05] START
Provisioning code: RF0010-20200407121356-000552322695-206.149.126.86
Serial Number: 57801T0182935
Sw version: AGAWI_4.0.7
[2020-04-09T11:38:19] WiFi: deauthenticated client 9c:b6:d0:be:bd:8d
[2020-04-09T11:38:20] WiFi: disconnected client 192.168.1.2 MAC 9c:b6:d0:be:bd:8d
[2020-04-09T11:38:20] LAN: disconnected host IP 192.168.1.2 MAC 9c:b6:d0:be:bd:8d (DHCP)
[2020-04-09T11:38:21] WiFi: disconnected client 9c:b6:d0:be:bd:8d
[2020-04-09T11:38:28] WiFi: detected client 9c:b6:d0:be:bd:8d
[2020-04-09T11:38:28] WiFi: detected client 9c:b6:d0:be:bd:8d
[2020-04-09T11:38:29] WiFi: authenticated client 9c:b6:d0:be:bd:8d
[2020-04-09T11:38:31] WiFi: detected client 192.168.1.2 MAC 9c:b6:d0:be:bd:8d (DHCP)
[2020-04-09T11:38:31] LAN: added host IP 192.168.1.2 MAC 9c:b6:d0:be:bd:8d (DHCP)
[2020-04-09T11:38:36] WiFi: disconnected client dc:0b:34:84:d5:12
[2020-04-09T11:38:51] WiFi: disconnected client 192.168.1.4 MAC f4:d6:20:72:66:7c
[2020-04-09T11:38:51] LAN: disconnected host IP 192.168.1.4 MAC f4:d6:20:72:66:7c (DHCP)
[2020-04-09T11:38:52] WiFi: disconnected client f4:d6:20:72:66:7c
[2020-04-09T11:40:43] WiFi: disconnected client 192.168.1.6 MAC c0:ee:fb:42:ce:37
[2020-04-09T11:40:43] LAN: disconnected host IP 192.168.1.6 MAC c0:ee:fb:42:ce:37 (DHCP)
[2020-04-09T11:41:06] WiFi: disconnected client 192.168.1.2 MAC 9c:b6:d0:be:bd:8d
[2020-04-09T11:41:06] LAN: disconnected host IP 192.168.1.2 MAC 9c:b6:d0:be:bd:8d (DHCP)
[2020-04-09T11:41:07] WiFi: detected client 192.168.1.2 MAC 9c:b6:d0:be:bd:8d (DHCP)
[2020-04-09T11:41:07] LAN: added host IP 192.168.1.2 MAC 9c:b6:d0:be:bd:8d (DHCP)
[2020-04-09T11:48:39] WiFi: detected client 192.168.1.6 MAC c0:ee:fb:42:ce:37 (DHCP)
[2020-04-09T11:48:39] LAN: added host IP 192.168.1.6 MAC c0:ee:fb:42:ce:37 (DHCP)
[2020-04-09T12:01:13] WiFi: disconnected client 192.168.1.6 MAC c0:ee:fb:42:ce:37
[2020-04-09T12:01:13] LAN: disconnected host IP 192.168.1.6 MAC c0:ee:fb:42:ce:37 (DHCP)
[2020-04-09T12:07:51] WiFi: detected client 192.168.1.6 MAC c0:ee:fb:42:ce:37 (DHCP)
[2020-04-09T12:07:51] LAN: added host IP 192.168.1.6 MAC c0:ee:fb:42:ce:37 (DHCP)
[2020-04-09T12:11:19] WiFi: disconnected client 192.168.1.6 MAC c0:ee:fb:42:ce:37
[2020-04-09T12:11:19] LAN: disconnected host IP 192.168.1.6 MAC c0:ee:fb:42:ce:37 (DHCP)
[2020-04-09T12:16:25] WiFi: disconnected client 192.168.1.2 MAC 9c:b6:d0:be:bd:8d
[2020-04-09T12:16:25] LAN: disconnected host IP 192.168.1.2 MAC 9c:b6:d0:be:bd:8d (DHCP)
[2020-04-09T12:18:37] WiFi: deauthenticated client 9c:b6:d0:be:bd:8d
[2020-04-09T12:18:37] WiFi: disconnected client 9c:b6:d0:be:bd:8d
[2020-04-09T12:18:48] WiFi: detected client 9c:b6:d0:be:bd:8d
[2020-04-09T12:18:48] WiFi: detected client 9c:b6:d0:be:bd:8d
[2020-04-09T12:18:48] WiFi: authenticated client 9c:b6:d0:be:bd:8d
[2020-04-09T12:18:51] WiFi: detected client 192.168.1.2 MAC 9c:b6:d0:be:bd:8d (DHCP)
[2020-04-09T12:18:51] LAN: added host IP 192.168.1.2 MAC 9c:b6:d0:be:bd:8d (DHCP)
[2020-04-09T12:19:16] END

If I read the log correctly:
- I manually connected to the network just after starting the log, at 11:38
- I've been automatically disconnected and reconnected at 11:41
- I've been disconnected again at 12:16, this time without being automatically reconnected
- at 12:18 I realized my network was down so I manually reconnected

@seth I don't know if you see anything useful in this log. I can't tell if this smells like a router problem or like a problem of my wifi card.

Edit: here is the journalctl log of my machine around the time when the presumed network fault happened.

Last edited by snack (2020-04-09 10:44:03)

Offline

#11 2020-04-09 10:38:19

snack
Member
From: Italy
Registered: 2009-01-13
Posts: 777

Re: Wifi card looses network connection

As for the cryptmode setting I got this error:

apr 08 17:13:52 stryke kernel: ath10k_pci 0000:3b:00.0: cryptmode > 0 requires raw mode support from firmware
apr 08 17:13:52 stryke kernel: ath10k_pci 0000:3b:00.0: fatal problem with firmware features: -22
apr 08 17:13:52 stryke kernel: ath10k_pci 0000:3b:00.0: could not probe fw (-22)

when booting with "ath10k_core.cryptmode=1", so I don't think there's much to be done along this way.

Offline

#12 2020-04-10 12:23:42

snack
Member
From: Italy
Registered: 2009-01-13
Posts: 777

Re: Wifi card looses network connection

@seth: I had the possibility to use an external usb WiFi antenna with my laptop:

$ lsusb
Bus 001 Device 013: ID 2357:0109 TP-Link TL WN823N RTL8192EU

With this device the network connection is rock solid, so I really think that the culprit must be the internal WiFI card. You spoke about enabling ath10k debug mode: can you give me a bit of guidance with this? Thanks.

Offline

#13 2020-04-10 13:36:53

seth
Member
Registered: 2012-09-03
Posts: 14,795

Offline

#14 2020-04-10 17:09:08

blake5634
Member
Registered: 2020-04-10
Posts: 6

Re: Wifi card looses network connection

In order to help the Arch community I'll offer that I have the exact same issue on same hardware using Kubuntu 18.04.   I updated Killer firmware about a month ago which finally fixed the problem, but the latest apt update broke it again.

Offline

#15 2020-04-10 20:33:32

snack
Member
From: Italy
Registered: 2009-01-13
Posts: 777

Re: Wifi card looses network connection

@seth: thanks, I'll try with the debug mode as soon as possible.

@blake5634: interesting, how did you upgrade the firmware? Is there a way to see which firmware version is currently installed? Thanks

Offline

#16 2020-04-10 21:04:00

blake5634
Member
Registered: 2020-04-10
Posts: 6

Re: Wifi card looses network connection

@snack     Just far enough back that I can't remember details.   I know I downloaded "ath10k-firmware-master.zip" from somewhere and there were some steps to install it.   I guess I could try to repeat the steps but it seems Kernel regression would not be fixed by that and may be the culprit.   Kind of the limit of my knowledge here.

Offline

#17 2020-04-11 06:03:51

seth
Member
Registered: 2012-09-03
Posts: 14,795

Re: Wifi card looses network connection

grep -r 'WLAN.RM.4.4.1-00140-QCARMSWPZ-1'  /usr/lib/firmware/ath10k/

You could try to move away /usr/lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin, see whether /usr/lib/firmware/ath10k/QCA6174/hw2.1/firmware-5.bin or /usr/lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin is succesfully loaded and whether that ha any impact on the situation.

Offline

#18 2020-04-11 14:08:03

blake5634
Member
Registered: 2020-04-10
Posts: 6

Re: Wifi card looses network connection

Thanks!    In ubunutu it's /lib, not /usr/lib, but from this I noted that I backed it up!
$ lls | head
total 36K
drwxrwxr-x 4 root root 4.0K Feb 26 09:02 QCA6174
drwxr-xr-x 4 root root 4.0K Feb  9  2019 QCA6174_BACKUP
drwxr-xr-x 3 root root 4.0K Feb  9  2019 QCA9377

So I'm going to try to go back to Feb 9 I guess. (If I have time for this!!)

Offline

#19 2020-04-11 20:26:33

snack
Member
From: Italy
Registered: 2009-01-13
Posts: 777

Re: Wifi card looses network connection

@seth I tried to enable the debug output as you suggested but the journal log got filled with an incredible amount of records, so I had to disable the debug mode. Then I moved on and removed firmware-6.bin and now my system is using firmware-4.bin:

$ ethtool -i wlan0
driver: ath10k_pci
version: 5.5.16-1-ck-skylake
firmware-version: WLAN.RM.2.0-00180-QCARMSWPZ-1
expansion-rom-version: 
bus-info: 0000:3b:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

$ grep -r WLAN.RM.2.0-00180-QCARMSWPZ-1 /usr/lib/firmware/ath10k/
Binary file /usr/lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin matches

I didn't experience any disconnection since 3 hours, while before they occurred usually within 1-2 hours form the network restart. Anyway I think it's too early to state that the problem is solved, so I'll keep monitoring the situation.

Offline

#20 2020-04-13 17:29:25

snack
Member
From: Italy
Registered: 2009-01-13
Posts: 777

Re: Wifi card looses network connection

After 9 hours I didn't experience any network fault, so I'd say that the firmware downgrade solved my problem. Thanks to blake5634 for the idea and to seth for the guidance! I think I should report the problem upstream since other people might be affected and probably the firmware has to be fixed and updated in linux-firmware (otherwise I fear that on next upgrade the problem will be back again).

@seth to your knowledge, is there a bug tracker for the firmware? From here I see there are several options for reporting driver bugs but I don't know what to do for firmware bugs. Thanks.

Offline

#21 2020-04-13 21:36:46

seth
Member
Registered: 2012-09-03
Posts: 14,795

Offline

#22 2020-04-15 16:41:56

blake5634
Member
Registered: 2020-04-10
Posts: 6

Re: Wifi card looses network connection

Update:  I reverted and did a cold reboot but that did not solve the problem.   Next I will try removing (renaming) firmware-6.bin to force reversion to firmware-4.bin.  Stay tuned.    For reference, here is  Dell's (Ubuntu specific) advice.

Offline

#23 2020-04-17 20:55:34

blake5634
Member
Registered: 2020-04-10
Posts: 6

Re: Wifi card looses network connection

OK - 48 hours after deleting firmware-6 and rebooting, wifi problems are not recurring. I think problem is now SOLVED.   Thanks Arch people.

Offline

#24 2020-04-27 06:47:53

snack
Member
From: Italy
Registered: 2009-01-13
Posts: 777

Re: Wifi card looses network connection

@blake5634 Upstream is trying to resolve the issue:

http://lists.infradead.org/pipermail/at … 14937.html

They are not able to reproduce the bug on their access points given my configuration, so it might help if you join the thread and provide information about your configuration.

Offline

#25 2020-05-03 08:44:18

Aliverix
Member
Registered: 2014-11-05
Posts: 12

Re: Wifi card looses network connection

@snack: I have your exact same problem, but with a different router, a Linksys E2500 v3. I am willing to help debugging, are you still in contact with the developers? Also, have you already tested other versions with API 6? We are on 140, I have tested 151 and it is also affected.

Anyway, today I deleted `firmware-6.bin` as well, I will report back if I have any issues.

Edit: it is probably a good idea to mention this in the wiki page for the XPS 9570.

Last edited by Aliverix (2020-05-03 08:45:53)

Offline

Board footer

Powered by FluxBB