Created attachment 1130283 [details] log output. Description of problem: The network driver crashes. Version-Release number of selected component (if applicable): kernel-core-4.3.5-300.fc23.x86_64 How reproducible: every time. Steps to Reproduce: 1.connect to wireless network. 2.suspend move to new location with a different wireless network 3. unsuspend, 4. connect wireless. Actual results: -on reconnection the wireless will initially connect, then after a period of time within 5 minutes, the connection will drop, and it was fixable with a soft reboot. -yesterday, a reboot didn't fix it. It reappeared with two soft reboots. - it is more likely to happen with a connection to a "web interface" for authentication, like our college, nm pops up a firefox window to log in, or mcdonalds/burger king type of authentication click to as either the 1st or 4th step listed. Expected results: Additional info: I haven't been as "scientific" about diagnosing this since it actually requires to move physical locations, which are a few miles away. It might not be the kernel -causing- it. I have also noticed coming out of suspend after moving, the list of available networks doesn't refresh, and I have had to "select network" to switch to a different network especially after the college web authentication page. Which is an odd bird because it also is like a single FF screen without the + for new tab type of window. I would be happy to help if you need anything more specific.
It happened again but it was a good half hour this time. sys-devices-pci0000:00-0000:00:1c.1-0000:02:00.0-net-wlp2s0.device loaded active plugged AR9285 Wireless Network Ada I couldn't unload the ath9k_hw module with modprobe. Even with the hardware switch disabling it. Disabling hardware switch doesn't fix it either. This in a Lenovo G560 portable.
I am having problems with the wireless, it borked on an AT&T U-verse router after coming out of suspend about 15 minutes into a session without connecting to the webpage login site since the last reboot. Bug 1305243 is also having issues with a Qualcomm Atheros, but with the Ethernet Adapter not the wireless. Possibly related? lspci -nn | grep -iE network\|ethernet 01:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8152 v2.0 Fast Ethernet [1969:2062] (rev c1) 02:00.0 Network controller [0280]: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)
The output has changed slightly in the logs. Feb 26 19:35:20 daffodil kernel: ath: phy0: RX failed to go idle in 10 ms RXSM=0xffffffff Feb 26 19:35:20 daffodil kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Feb 26 19:35:25 daffodil kernel: ath: phy0: Failed to wakeup in 500us Feb 26 19:35:25 daffodil kernel: ath: phy0: RX failed to go idle in 10 ms RXSM=0xffffffff Feb 26 19:35:25 daffodil kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Feb 26 19:35:30 daffodil kernel: ath: phy0: Failed to wakeup in 500us Feb 26 19:35:30 daffodil chronyd[840]: Can't synchronise: no selectable sources Feb 26 19:35:30 daffodil kernel: ath: phy0: RX failed to go idle in 10 ms RXSM=0xffffffff Feb 26 19:35:30 daffodil kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Feb 26 19:35:35 daffodil kernel: ath: phy0: Failed to wakeup in 500us Feb 26 19:35:35 daffodil kernel: ath: phy0: RX failed to go idle in 10 ms RXSM=0xffffffff Feb 26 19:35:35 daffodil kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Happened again twice, after the latest update to kernel-4.4.2-301.fc23.x86_64. The second time thelaptop was plugged in, and had not moved since the last reboot.
Yesterday's update 4.4.3-300.fc23.x86_64, if it didn't fix it, slowed the rate of occurrence down. It hasn't happened since the update. I also installed all the stuff to rebuild the kernel and poke through the source at about the same time. The ghosting of the wireless networks also seemed to disappear coming out of suspend at the same time.
It started happening again about every 45 minutes after yesterdays update: Mar 04 11:46:41 INFO Upgraded: NetworkManager.x86_64 1:1.0.10-3.fc23 NetworkManager-adsl.x86_64 1:1.0.10-3.fc23 NetworkManager-bluetooth.x86_64 1:1.0.10-3.fc23 NetworkManager-config-connectivity-fedora.x86_64 1:1.0.10-3.fc23 NetworkManager-glib.x86_64 1:1.0.10-3.fc23 NetworkManager-libnm.x86_64 1:1.0.10-3.fc23 NetworkManager-team.x86_64 1:1.0.10-3.fc23 NetworkManager-wifi.x86_64 1:1.0.10-3.fc23 NetworkManager-wwan.x86_64 1:1.0.10-3.fc23 exiv2-libs.x86_64 0.25-3.fc23 fedora-cert.noarch 0.5.10.7-1.fc23 fedora-packager.noarch 0.5.10.7-1.fc23 java-1.8.0-openjdk-headless.x86_64 1:1.8.0.72-9.b16.fc23 koji.noarch 1.10.1-3.fc23 krb5-devel.x86_64 1.14.1-1.fc23 krb5-libs.x86_64 1.14.1-1.fc23 krb5-workstation.x86_64 1.14.1-1.fc23 libinput.x86_64 1.2.1-2.fc23 libseccomp.x86_64 2.3.0-0.fc23 libudisks2.x86_64 2.1.7-1.fc23 libv4l.x86_64 1.10.0-2.fc23 openssl.x86_64 1:1.0.2g-2.fc23 openssl-devel.x86_64 1:1.0.2g-2.fc23 openssl-libs.x86_64 1:1.0.2g-2.fc23 pcre.x86_64 8.38-7.fc23 pcre-devel.x86_64 8.38-7.fc23 perl.x86_64 4:5.22.1-351.fc23 perl-ExtUtils-Embed.noarch 1.32-351.fc23 perl-devel.x86_64 4:5.22.1-351.fc23 perl-libs.x86_64 4:5.22.1-351.fc23 perl-macros.x86_64 4:5.22.1-351.fc23 udisks2.x86_64 2.1.7-1.fc23 ---- The day before's updates were: Installed: kernel.x86_64 4.4.3-300.fc23 kernel-core.x86_64 4.4.3-300.fc23 kernel-debug-devel.x86_64 4.4.3-300.fc23 kernel-modules.x86_64 4.4.3-300.fc23 libsss_autofs.x86_64 1.13.3-5.fc23 Upgraded: graphite2.x86_64 1.3.6-1.fc23 kernel-headers.x86_64 4.4.3-300.fc23 libipa_hbac.x86_64 1.13.3-5.fc23 libsss_idmap.x86_64 1.13.3-5.fc23 libsss_nss_idmap.x86_64 1.13.3-5.fc23 libsss_sudo.x86_64 1.13.3-5.fc23 nspr.x86_64 4.12.0-1.fc23 nss.x86_64 3.22.2-1.0.fc23 nss-softokn.x86_64 3.22.2-1.0.fc23 nss-softokn-freebl.x86_64 3.22.2-1.0.fc23 nss-sysinit.x86_64 3.22.2-1.0.fc23 nss-tools.x86_64 3.22.2-1.0.fc23 nss-util.x86_64 3.22.2-1.0.fc23 pcre.x86_64 8.38-6.fc23 python3-sssdconfig.noarch 1.13.3-5.fc23 python3-urllib3.noarch 1.13.1-3.fc23 rpm.x86_64 4.13.0-0.rc1.12.fc23 rpm-build.x86_64 4.13.0-0.rc1.12.fc23 rpm-build-libs.x86_64 4.13.0-0.rc1.12.fc23 rpm-libs.x86_64 4.13.0-0.rc1.12.fc23 rpm-plugin-selinux.x86_64 4.13.0-0.rc1.12.fc23 rpm-plugin-systemd-inhibit.x86_64 4.13.0-0.rc1.12.fc23 rpm-python.x86_64 4.13.0-0.rc1.12.fc23 rpm-python3.x86_64 4.13.0-0.rc1.12.fc23 sssd.x86_64 1.13.3-5.fc23 sssd-ad.x86_64 1.13.3-5.fc23 sssd-client.x86_64 1.13.3-5.fc23 sssd-common.x86_64 1.13.3-5.fc23 sssd-common-pac.x86_64 1.13.3-5.fc23 sssd-ipa.x86_64 1.13.3-5.fc23 sssd-krb5.x86_64 1.13.3-5.fc23 sssd-krb5-common.x86_64 1.13.3-5.fc23 sssd-ldap.x86_64 1.13.3-5.fc23 sssd-proxy.x86_64 1.13.3-5.fc23
Created attachment 1133603 [details] system log I am adding the system log. From wake up to the reboot. 2 of the 3 times it has crashed since the last update it was within like 5 minutes of coming out of suspend. It went two days with 1.5 crashes per day, which is an improvement. :)
I forgot to mention the last update was: Mar 05 09:40:47 INFO Upgraded: glibc-common-2.22-11.fc23.x86_64 Mar 05 09:40:50 INFO Upgraded: glibc-2.22-11.fc23.x86_64 Mar 05 09:40:50 INFO Upgraded: glusterfs-libs-3.7.8-2.fc23.x86_64 Mar 05 09:40:51 INFO Upgraded: glusterfs-3.7.8-2.fc23.x86_64 Mar 05 09:40:52 INFO Upgraded: glusterfs-client-xlators-3.7.8-2.fc23.x86_64 Mar 05 09:40:54 INFO Upgraded: glibc-headers-2.22-11.fc23.x86_64 Mar 05 09:40:55 INFO Upgraded: librados2-1:0.94.6-1.fc23.x86_64 Mar 05 09:41:02 INFO Upgraded: selinux-policy-3.13.1-158.9.fc23.noarch Mar 05 09:41:12 INFO Upgraded: selinux-policy-targeted-3.13.1-158.9.fc23.noarch Mar 05 09:41:13 INFO Upgraded: librbd1-1:0.94.6-1.fc23.x86_64 Mar 05 09:41:14 INFO Upgraded: glibc-devel-2.22-11.fc23.x86_64 Mar 05 09:41:14 INFO Upgraded: glusterfs-fuse-3.7.8-2.fc23.x86_64 Mar 05 09:41:14 INFO Upgraded: glusterfs-api-3.7.8-2.fc23.x86_64 Mar 05 09:41:15 INFO Upgraded: geocode-glib-3.18.2-1.fc23.x86_64 Mar 05 09:41:16 INFO Upgraded: libbluray-0.9.2-1.fc23.x86_64 Mar 05 09:41:16 INFO Upgraded: parted-3.2-16.fc23.x86_64
it is still happening. IF you do an ifconfig down, you can get rmmod to work. It was happening about 5 minutes after a reboot. It backs off for quite a bit longer IE it made it overnight after removing and inserting the module then rebooting. Mar 09 15:34:19 daffodil kernel: ath: phy0: Failed to wakeup in 500us Mar 09 15:34:19 daffodil kernel: ath: phy0: RX failed to go idle in 10 ms RXSM=0xffffffff Mar 09 15:34:19 daffodil kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Mar 09 15:34:22 daffodil kernel: ath: phy0: Failed to wakeup in 500us Mar 09 15:34:22 daffodil systemd[1]: Stopping Load/Save RF Kill Switch Status of rfkill1... Mar 09 15:34:22 daffodil kernel: ath9k: ath9k: Driver unloaded Mar 09 15:34:22 daffodil NetworkManager[1008]: <info> radio killswitch /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/ieee80211/phy0/rfkill1 disappeared Mar 09 15:34:22 daffodil NetworkManager[1008]: <info> (wlp2s0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36] Mar 09 15:34:22 daffodil systemd[1]: Stopped Load/Save RF Kill Switch Status of rfkill1. Mar 09 15:34:22 daffodil audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill@rfkill1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 09 15:34:22 daffodil NetworkManager[1008]: <warn> (wlp2s0): failed to disable userspace IPv6LL address handling Mar 09 15:34:32 daffodil audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 09 15:35:09 daffodil kernel: ath9k: module verification failed: signature and/or required key missing - tainting kernel Mar 09 15:35:09 daffodil kernel: ath9k 0000:02:00.0: enabling device (0000 -> 0002) Mar 09 15:35:09 daffodil kernel: ath: phy1: Mac Chip Rev 0xfffc0.f is not supported by this driver Mar 09 15:35:09 daffodil kernel: ath: phy1: Unable to initialize hardware; initialization status: -95 Mar 09 15:35:09 daffodil kernel: ath9k 0000:02:00.0: Failed to initialize device Mar 09 15:35:09 daffodil kernel: ath9k: probe of 0000:02:00.0 failed with error -95 Mar 09 15:35:32 daffodil upowerd[1328]: (upowerd:1328): UPower-Linux-WARNING **: failed to coldplug unifying device: Attempt to read response from device timed out Mar 09 15:36:07 daffodil NetworkManager[1008]: <info> connectivity: check for uri 'http://fedoraproject.org/static/hotspot.txt' failed with 'Error resolving 'fedoraproject.org': No address associated with hostname' Mar 09 15:36:25 daffodil NetworkManager[1008]: <info> WiFi now disabled by radio killswitch Mar 09 15:36:25 daffodil NetworkManager[1008]: <info> WWAN hardware radio set disabled Mar 09 15:36:33 daffodil NetworkManager[1008]: <info> WiFi now enabled by radio killswitch
I recompiled the 4.4.3 kernel without the patches: ath9k-rx-dma-stop-check.patch unix-correctly-track-in-flight-fds-in-sending-proces.patch and just without ath9k-rx-dma-stop-check.patch I haven't been nearly as mobile this week as normal so this maybe an anomally but it has only happened once with just the single ath9k patch removed, and it hasn't happened at all with the both patches removed. Incidentally, the unix-correctly-track-in-flight-fds-in-sending-proces.patch didn't apply to the 4.5 development kernel..(I ended up killing that build, because it takes about 3 hours to fully complete a kernel build, and you can't put it in suspend or restart the build in the middle, or at least I couldn't figure out how..)
The last update which was: device-mapper-persistent-data x86_64 0.6.2-0.1.rc6.fc23 updates 427 k evince x86_64 3.18.2-4.fc23 updates 2.3 M evince-browser-plugin x86_64 3.18.2-4.fc23 updates 62 k evince-djvu x86_64 3.18.2-4.fc23 updates 54 k evince-libs x86_64 3.18.2-4.fc23 updates 360 k evince-nautilus x86_64 3.18.2-4.fc23 updates 43 k glusterfs x86_64 3.7.8-3.fc23 updates 450 k glusterfs-api x86_64 3.7.8-3.fc23 updates 85 k glusterfs-client-xlators x86_64 3.7.8-3.fc23 updates 774 k glusterfs-fuse x86_64 3.7.8-3.fc23 updates 135 k glusterfs-libs x86_64 3.7.8-3.fc23 updates 338 k libsmbclient x86_64 2:4.3.6-0.fc23 updates 122 k libwbclient x86_64 2:4.3.6-0.fc23 updates 96 k samba-client x86_64 2:4.3.6-0.fc23 updates 549 k samba-client-libs x86_64 2:4.3.6-0.fc23 updates 4.6 M samba-common noarch 2:4.3.6-0.fc23 updates 185 k samba-common-libs x86_64 2:4.3.6-0.fc23 updates 158 k traceroute x86_64 3:2.0.22-1.fc23 updates 64 k -- seemed to make it a lot more stable. The network hasn't crashed since.
It is back after the last update. I am including some of the logs.. rngd is coming up with an error but that has been happening for a while. It immediately crashed the first two reboots after installing the updates. I got one to the network with 1 boot for 5-10 minutes, then it crashed again, the next reboot it crashed or never connected. I am reverting to the kernel without the unix--whatever patch, and without the ath--whatever patch that was previously mentioned. I am including some logs. If it isn't enough let me know. This is the last update: autocorr-en.noarch 1:5.0.5.2-6.fc23 bind-libs.x86_64 32:9.10.3-12.P4.fc23 bind-libs-lite.x86_64 32:9.10.3-12.P4.fc23 bind-license.noarch 32:9.10.3-12.P4.fc23 bind-utils.x86_64 32:9.10.3-12.P4.fc23 bind99-libs.x86_64 9.9.8-4.P4.fc23 bind99-license.noarch 9.9.8-4.P4.fc23 binutils.x86_64 2.25-17.fc23 binutils-devel.x86_64 2.25-17.fc23 dnf.noarch 1.1.7-2.fc23 dnf-conf.noarch 1.1.7-2.fc23 dnf-plugins-core.noarch 0.1.17-1.fc23 dnf-yum.noarch 1.1.7-2.fc23 gnome-terminal.x86_64 3.18.3-1.fc23 gtk-update-icon-cache.x86_64 3.18.9-1.fc23 gtk2.x86_64 2.24.30-1.fc23 gtk3.x86_64 3.18.9-1.fc23 libinput.x86_64 1.2.1-4.fc23 libreoffice-calc.x86_64 1:5.0.5.2-6.fc23 libreoffice-core.x86_64 1:5.0.5.2-6.fc23 libreoffice-draw.x86_64 1:5.0.5.2-6.fc23 libreoffice-emailmerge.x86_64 1:5.0.5.2-6.fc23 libreoffice-filters.x86_64 1:5.0.5.2-6.fc23 libreoffice-graphicfilter.x86_64 1:5.0.5.2-6.fc23 libreoffice-impress.x86_64 1:5.0.5.2-6.fc23 libreoffice-math.x86_64 1:5.0.5.2-6.fc23 libreoffice-opensymbol-fonts.noarch 1:5.0.5.2-6.fc23 libreoffice-pdfimport.x86_64 1:5.0.5.2-6.fc23 libreoffice-pyuno.x86_64 1:5.0.5.2-6.fc23 libreoffice-ure.x86_64 1:5.0.5.2-6.fc23 libreoffice-writer.x86_64 1:5.0.5.2-6.fc23 libreoffice-xsltfilter.x86_64 1:5.0.5.2-6.fc23 libsolv.x86_64 0.6.19-2.fc23 man-db.x86_64 2.7.1-11.fc23 mutter.x86_64 3.18.3-2.fc23 openssh.x86_64 7.2p2-1.fc23 openssh-askpass.x86_64 7.2p2-1.fc23 openssh-clients.x86_64 7.2p2-1.fc23 openssh-server.x86_64 7.2p2-1.fc23 orc.x86_64 0.4.25-1.fc23 python3-dnf.noarch 1.1.7-2.fc23 python3-dnf-plugins-core.noarch 0.1.17-1.fc23 rygel.x86_64 0.28.3-1.fc23 ---rngd-- this has been happening for a while.. Mar 16 17:43:54 daffodil rngd[848]: read error Mar 16 17:43:54 daffodil rngd[848]: read error Mar 16 17:43:54 daffodil rngd[848]: read error Mar 16 17:43:54 daffodil rngd[848]: read error --dhcp it doesn't look like it is failing down to ipv4-- Mar 16 17:44:47 daffodil dhclient[1207]: XMT: Solicit on wlp2s0, interval 37140ms. Mar 16 17:44:47 daffodil dhclient[1207]: RCV: Advertise message on wlp2s0 from fe80::ba16:19ff:fe5d:1cc0. Mar 16 17:44:47 daffodil dhclient[1207]: message status code NoAddrsAvail: "No addresses available for this interface." Mar 16 17:44:56 daffodil NetworkManager[1001]: <warn> (wlp2s0): DHCPv6 request timed out. Mar 16 17:44:56 daffodil NetworkManager[1001]: <info> (wlp2s0): DHCPv6 state changed unknown -> timeout Mar 16 17:44:56 daffodil NetworkManager[1001]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 1207 Mar 16 17:44:56 daffodil NetworkManager[1001]: <info> (wlp2s0): DHCPv6 state changed timeout -> done --this is where it shows up with the atheros driver and goes into the infinite loop--- Mar 16 18:12:25 daffodil dbus[861]: [system] Failed to activate service 'org.bluez': timed out Mar 16 18:12:22 daffodil audit[2599]: CRED_REFR pid=2599 uid=0 auid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c102 Mar 16 18:12:25 daffodil pulseaudio[2039]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: D Mar 16 18:12:22 daffodil audit[2599]: USER_START pid=2599 uid=0 auid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c10 Mar 16 18:12:33 daffodil audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sy Mar 16 18:12:41 daffodil audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sy Mar 16 18:12:50 daffodil kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Mar 16 18:12:50 daffodil kernel: ath: phy0: Chip reset failed Mar 16 18:12:50 daffodil kernel: ath: phy0: Unable to reset channel, reset status -22 Mar 16 18:12:51 daffodil kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Mar 16 18:12:51 daffodil kernel: ath: phy0: Chip reset failed Mar 16 18:12:51 daffodil kernel: ath: phy0: Unable to reset channel, reset status -22 Mar 16 18:12:51 daffodil kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Mar 16 18:12:51 daffodil kernel: ath: phy0: Chip reset failed Mar 16 18:12:51 daffodil kernel: ath: phy0: Unable to reset channel, reset status -22 Mar 16 18:12:51 daffodil kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Mar 16 18:12:51 daffodil kernel: ath: phy0: Chip reset failed Mar 16 18:12:51 daffodil kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Mar 16 18:12:51 daffodil kernel: ath: phy0: Chip reset failed Mar 16 18:12:51 daffodil kernel: ath: phy0: Unable to reset channel, reset status -22 Mar 16 18:12:51 daffodil NetworkManager[1001]: <warn> Connection disconnected (reason -4) Mar 16 18:12:51 daffodil kernel: cfg80211: World regulatory domain updated: Mar 16 18:12:51 daffodil kernel: cfg80211: DFS Master region: unset Mar 16 18:12:51 daffodil kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Mar 16 18:12:51 daffodil kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Mar 16 18:12:51 daffodil kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) Mar 16 18:12:51 daffodil kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) Mar 16 18:12:51 daffodil kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) Mar 16 18:12:51 daffodil kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) Mar 16 18:12:51 daffodil kernel: cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) Mar 16 18:12:51 daffodil kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Mar 16 18:12:51 daffodil kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) Mar 16 18:12:51 daffodil NetworkManager[1001]: <info> (wlp2s0): supplicant interface state: completed -> disconnected Mar 16 18:12:51 daffodil kernel: cfg80211: Regulatory domain changed to country: US Mar 16 18:12:51 daffodil kernel: cfg80211: DFS Master region: FCC Mar 16 18:12:51 daffodil kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Mar 16 18:12:51 daffodil kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A) Mar 16 18:12:51 daffodil kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (N/A) Mar 16 18:12:51 daffodil kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s) Mar 16 18:12:51 daffodil kernel: cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s) Mar 16 18:12:51 daffodil kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A) Mar 16 18:12:51 daffodil kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A) Mar 16 18:12:51 daffodil kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Mar 16 18:12:52 daffodil kernel: ath: phy0: Chip reset failed Mar 16 18:12:52 daffodil kernel: ath: phy0: Unable to reset channel, reset status -22 Mar 16 18:12:52 daffodil NetworkManager[1001]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning Mar 16 18:12:52 daffodil kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Mar 16 18:12:52 daffodil kernel: ath: phy0: Chip reset failed Mar 16 18:12:52 daffodil kernel: ath: phy0: Unable to reset channel, reset status -22 Mar 16 18:12:52 daffodil kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Mar 16 18:12:52 daffodil kernel: ath: phy0: Chip reset failed Mar 16 18:12:52 daffodil kernel: ath: phy0: Unable to reset channel, reset status -22 Mar 16 18:12:52 daffodil kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Mar 16 18:12:52 daffodil kernel: ath: phy0: Chip reset failed
I built the 4.4.6 kernel, and if the hardware switch gets turned on, or I boot with it on I get this: Mar 25 16:16:20 daffodil NetworkManager[1013]: <info> WiFi now enabled by radio killswitch Mar 25 16:16:20 daffodil kernel: ath: phy0: hw.c ath9k_hw_chip_reset succeded. Mar 25 16:16:20 daffodil kernel: BUG: unable to handle kernel paging request at ffffc90002800000 Mar 25 16:16:20 daffodil kernel: IP: [<ffffffff813ce5de>] ioread32+0x2e/0x40 Mar 25 16:16:20 daffodil kernel: PGD 13b0a8067 PUD 13b0a9067 PMD 0 Mar 25 16:16:20 daffodil kernel: Oops: 0000 [#1] SMP Mar 25 16:16:20 daffodil kernel: Modules linked in: fuse(E) xt_CHECKSUM(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) tun(E) nf_conntrack_netbios_ns(E) nf_conntrack_broadcast(E) ip6t_rpfilter(E) ip6t_REJECT(E) nf_reject_ipv6(E) xt_conntrack(E) ip_set(E) nfnetlink(E) ebtable_nat(E) ebtable_filter(E) ebtable_broute(E) bridge(E) stp(E) llc(E) ebtables(E) ip6table_mangle(E) ip6table_nat(E) nf_conntrack_ipv6(E) nf_defrag_ipv6(E) nf_nat_ipv6(E) ip6table_raw(E) ip6table_security(E) ip6table_filter(E) ip6_tables(E) iptable_mangle(E) iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack(E) iptable_raw(E) iptable_security(E) rtsx_usb_ms(E) memstick(E) intel_rapl(E) snd_hda_codec_hdmi(E) iosf_mbi(E) arc4(E) snd_hda_codec_conexant(E) x86_pkg_temp_thermal(E) coretemp(E) snd_hda_codec_generic(E) Mar 25 16:16:20 daffodil kernel: ath9k(E) ath9k_common(E) kvm_intel(E) uvcvideo(E) ath9k_hw(E) snd_hda_intel(E) snd_hda_codec(E) videobuf2_vmalloc(E) videobuf2_memops(E) videobuf2_v4l2(E) snd_hda_core(E) videobuf2_core(E) iTCO_wdt(E) v4l2_common(E) kvm(E) snd_hwdep(E) iTCO_vendor_support(E) videodev(E) media(E) snd_seq(E) snd_seq_device(E) snd_pcm(E) ath(E) snd_timer(E) snd(E) ideapad_laptop(E) irqbypass(E) mac80211(E) sparse_keymap(E) crct10dif_pclmul(E) cfg80211(E) crc32_pclmul(E) rfkill(E) soundcore(E) wmi(E) crc32c_intel(E) shpchp(E) mei_me(E) mei(E) lpc_ich(E) i2c_i801(E) joydev(E) tpm_tis(E) tpm(E) nfsd(E) auth_rpcgss(E) nfs_acl(E) lockd(E) grace(E) sunrpc(E) i915(E) hid_logitech_hidpp(E) i2c_algo_bit(E) drm_kms_helper(E) drm(E) serio_raw(E) atl1c(E) fjes(E) video(E) rtsx_usb_sdmmc(E) mmc_core(E) hid_logitech_dj(E) Mar 25 16:16:20 daffodil kernel: rtsx_usb(E) Mar 25 16:16:20 daffodil kernel: CPU: 1 PID: 1013 Comm: NetworkManager Tainted: G E 4.4.6-301.fc23.x86_64 #1 Mar 25 16:16:20 daffodil kernel: Hardware name: LENOVO 4334 /Base Board Product Name, BIOS 40CN28WW(V2.14) 10/07/2011 Mar 25 16:16:20 daffodil kernel: task: ffff8800b65e0000 ti: ffff8800b1f20000 task.ti: ffff8800b1f20000 Mar 25 16:16:20 daffodil kernel: RIP: 0010:[<ffffffff813ce5de>] [<ffffffff813ce5de>] ioread32+0x2e/0x40 Mar 25 16:16:20 daffodil kernel: RSP: 0018:ffff8800b1f23618 EFLAGS: 00010092 Mar 25 16:16:20 daffodil kernel: RAX: 0000000000000001 RBX: ffff8800b71694c0 RCX: 0000000000000000 Mar 25 16:16:20 daffodil kernel: RDX: ffff8800b6980028 RSI: ffffc90002800000 RDI: ffffc90002800000 Mar 25 16:16:20 daffodil kernel: RBP: ffff8800b1f23640 R08: ffff8800b7168f20 R09: 0000000000000000 Mar 25 16:16:20 daffodil kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8800b6980078 Mar 25 16:16:20 daffodil kernel: R13: 0000000000000000 R14: ffff8800b716ad50 R15: ffff8800b7168700 Mar 25 16:16:20 daffodil kernel: FS: 00007fcc75df18c0(0000) GS:ffff88013fa40000(0000) knlGS:0000000000000000 Mar 25 16:16:20 daffodil kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 25 16:16:20 daffodil kernel: CR2: ffffc90002800000 CR3: 00000000aed31000 CR4: 00000000000406e0 Mar 25 16:16:20 daffodil kernel: Stack: Mar 25 16:16:20 daffodil kernel: ffffffffa06c4e40 ffff8800b71694c0 ffff8800b6980028 ffff8800b6980078 Mar 25 16:16:20 daffodil kernel: 0000000000000000 ffff8800b1f23670 ffffffffa06589a1 ffff8800b71694c0 Mar 25 16:16:20 daffodil kernel: 00000000ffffffff ffff8800b7169ec8 ffff8800b716ad50 ffff8800b1f236c0 Mar 25 16:16:20 daffodil kernel: Call Trace: Mar 25 16:16:20 daffodil kernel: [<ffffffffa06c4e40>] ? ath9k_ioread32+0x30/0x80 [ath9k] Mar 25 16:16:20 daffodil kernel: [<ffffffffa06589a1>] ath9k_hw_setrxabort+0x21/0x150 [ath9k_hw] Mar 25 16:16:20 daffodil kernel: [<ffffffffa06c7839>] ath9k_config+0x199/0x1f0 [ath9k] Mar 25 16:16:20 daffodil kernel: [<ffffffffa03f2c0d>] ieee80211_hw_config+0x8d/0x370 [mac80211] Mar 25 16:16:20 daffodil kernel: [<ffffffffa0408724>] ieee80211_do_open+0x584/0x940 [mac80211] Mar 25 16:16:20 daffodil kernel: [<ffffffffa0408b38>] ieee80211_open+0x58/0x60 [mac80211] Mar 25 16:16:20 daffodil kernel: [<ffffffff8168c0c8>] __dev_open+0xc8/0x140 Mar 25 16:16:20 daffodil kernel: [<ffffffff8168c3dd>] __dev_change_flags+0x9d/0x160 Mar 25 16:16:20 daffodil kernel: [<ffffffff8168c4c9>] dev_change_flags+0x29/0x70 Mar 25 16:16:20 daffodil kernel: [<ffffffff8169a4b3>] do_setlink+0x633/0xb80 Mar 25 16:16:20 daffodil kernel: [<ffffffff811ce52c>] ? zone_statistics+0x7c/0xa0 Mar 25 16:16:20 daffodil kernel: [<ffffffff811b63cf>] ? get_page_from_freelist+0x4cf/0xb10 Mar 25 16:16:20 daffodil kernel: [<ffffffff810dc654>] ? set_next_entity+0xa4/0x870 Mar 25 16:16:20 daffodil kernel: [<ffffffff813e1822>] ? nla_parse+0x32/0x100 Mar 25 16:16:20 daffodil kernel: [<ffffffff8169b0ea>] rtnl_newlink+0x5aa/0x8a0 Mar 25 16:16:20 daffodil kernel: [<ffffffff813c6b79>] ? flex_array_get_ptr+0x9/0x20 Mar 25 16:16:20 daffodil kernel: [<ffffffff81336408>] ? security_capable+0x48/0x60 Mar 25 16:16:20 daffodil kernel: [<ffffffff810ac919>] ? ns_capable+0x29/0x50 Mar 25 16:16:20 daffodil kernel: [<ffffffff81699766>] rtnetlink_rcv_msg+0xe6/0x230 Mar 25 16:16:20 daffodil kernel: [<ffffffff8133b750>] ? sock_has_perm+0x70/0x90 Mar 25 16:16:20 daffodil kernel: [<ffffffff81699680>] ? rtnetlink_rcv+0x30/0x30 Mar 25 16:16:20 daffodil kernel: [<ffffffff816bf0f4>] netlink_rcv_skb+0xa4/0xc0 Mar 25 16:16:20 daffodil kernel: [<ffffffff81699678>] rtnetlink_rcv+0x28/0x30 Mar 25 16:16:20 daffodil kernel: [<ffffffff816be8aa>] netlink_unicast+0x12a/0x1b0 Mar 25 16:16:20 daffodil kernel: [<ffffffff816bedd2>] netlink_sendmsg+0x4a2/0x5f0 Mar 25 16:16:20 daffodil kernel: [<ffffffff8166c828>] sock_sendmsg+0x38/0x50 Mar 25 16:16:20 daffodil kernel: [<ffffffff8166d2d9>] ___sys_sendmsg+0x289/0x2a0 Mar 25 16:16:20 daffodil kernel: [<ffffffff816700fa>] ? sock_def_readable+0x3a/0x60 Mar 25 16:16:20 daffodil kernel: [<ffffffff8166c828>] ? sock_sendmsg+0x38/0x50 Mar 25 16:16:20 daffodil kernel: [<ffffffff8166ce67>] ? SYSC_sendto+0x157/0x190 Mar 25 16:16:20 daffodil kernel: [<ffffffff8124aca5>] ? __fget_light+0x25/0x60 Mar 25 16:16:20 daffodil kernel: [<ffffffff8166dc31>] __sys_sendmsg+0x51/0x90 Mar 25 16:16:20 daffodil kernel: [<ffffffff8166dc82>] SyS_sendmsg+0x12/0x20 Mar 25 16:16:20 daffodil kernel: [<ffffffff817a05ae>] entry_SYSCALL_64_fastpath+0x12/0x71 Mar 25 16:16:20 daffodil kernel: Code: ff ff 03 00 77 25 48 81 ff 00 00 01 00 76 05 0f b7 d7 ed c3 55 48 c7 c6 72 b4 a9 81 48 89 e5 e8 19 ff ff ff b8 ff ff ff ff 5d c3 <8b> 07 c3 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 81 fe Mar 25 16:16:20 daffodil kernel: RIP [<ffffffff813ce5de>] ioread32+0x2e/0x40 ----- I added some very basic debugging output which is why you see: Mar 25 16:16:20 daffodil kernel: ath: phy0: hw.c ath9k_hw_chip_reset succeded. Here is the patch for that. --- diff --git a/drivers/net/wireless/ath/ath9k/hw.c b/drivers/net/wireless/ath/ath9k/hw.c index e7a3101..586a11a 100644 --- a/drivers/net/wireless/ath/ath9k/hw.c +++ b/drivers/net/wireless/ath/ath9k/hw.c @@ -1488,18 +1488,22 @@ static bool ath9k_hw_chip_reset(struct ath_hw *ah, (REG_READ(ah, AR_CR) & AR_CR_RXE)) reset_type = ATH9K_RESET_COLD; - if (!ath9k_hw_set_reset_reg(ah, reset_type)) + if (!ath9k_hw_set_reset_reg(ah, reset_type)){ + ath_err(ath9k_hw_common(ah), "hw.c ath9k_hw_chip_reset ath9k_hw_set_reset_reg failed.\n"); return false; + } - if (!ath9k_hw_setpower(ah, ATH9K_PM_AWAKE)) + if (!ath9k_hw_setpower(ah, ATH9K_PM_AWAKE)){ + ath_err(ath9k_hw_common(ah), "hw.c ath9k_hw_chip_reset ath9k_hw_setpower failed.\n"); return false; + } ah->chip_fullsleep = false; if (AR_SREV_9330(ah)) ar9003_hw_internal_regulator_apply(ah); ath9k_hw_init_pll(ah, chan); - + ath_err(ath9k_hw_common(ah), "hw.c ath9k_hw_chip_reset succeded.\n"); return true; } @@ -2175,6 +2179,10 @@ static bool ath9k_hw_set_power_awake(struct ath_hw *ah) ath_err(ath9k_hw_common(ah), "Failed to wakeup in %uus\n", POWER_UP_TIME / 20); + ath_err(ath9k_hw_common(ah), + "hw.c ath9k_hw_set_power_awake Succeded to wakeup in %uus\n", + POWER_UP_TIME / 20); + return false; } @@ -2182,6 +2190,10 @@ static bool ath9k_hw_set_power_awake(struct ath_hw *ah) ar9003_mci_set_power_awake(ah); REG_CLR_BIT(ah, AR_STA_ID1, AR_STA_ID1_PWR_SAV); + ath_err(ath9k_hw_common(ah), + "hw.c ath9k_hw_set_power_awake Succeded to wakeup in %uus\n", + POWER_UP_TIME / 20); + return true; } diff --git a/drivers/net/wireless/ath/ath9k/mac.c b/drivers/net/wireless/ath/ath9k/mac.c index bba85d1..a7b8c28 100644 --- a/drivers/net/wireless/ath/ath9k/mac.c +++ b/drivers/net/wireless/ath/ath9k/mac.c @@ -638,6 +638,12 @@ EXPORT_SYMBOL(ath9k_hw_rxprocdesc); bool ath9k_hw_setrxabort(struct ath_hw *ah, bool set) { u32 reg; + ath_err(ath9k_hw_common(ah), + "mac.c ath9k_hw_setrxabort RX started + idle in 10 ms set=%d,RXSM=0x%x, + AR_OBS_BUS_1_RX_STATE=0x%x\n", + REG_READ(ah, AR_OBS_BUS_1), + REG_READ(ah, AR_OBS_BUS_1_RX_STATE) ); if (set) { REG_SET_BIT(ah, AR_DIAG_SW, @@ -653,6 +659,12 @@ bool ath9k_hw_setrxabort(struct ath_hw *ah, bool set) ath_err(ath9k_hw_common(ah), "RX failed to go idle in 10 ms RXSM=0x%x\n", reg); + ath_err(ath9k_hw_common(ah), + "mac.c ath9k_hw_setrxabort RX failed to go + idle in 10 ms set=%d,RXSM=0x%x, + AR_OBS_BUS_1_RX_STATE=0x%x\n", + REG_READ(ah, AR_OBS_BUS_1), + REG_READ(ah, AR_OBS_BUS_1_RX_STATE) ); return false; } @@ -660,6 +672,12 @@ bool ath9k_hw_setrxabort(struct ath_hw *ah, bool set) REG_CLR_BIT(ah, AR_DIAG_SW, (AR_DIAG_RX_DIS | AR_DIAG_RX_ABORT)); } + ath_err(ath9k_hw_common(ah), + "mac.c ath9k_hw_setrxabort RX succeded to go + idle in 10 ms set=%d,RXSM=0x%x, + AR_OBS_BUS_1_RX_STATE=0x%x\n", + REG_READ(ah, AR_OBS_BUS_1), + REG_READ(ah, AR_OBS_BUS_1_RX_STATE) ); return true; } @@ -693,8 +711,15 @@ bool ath9k_hw_stopdmarecv(struct ath_hw *ah, bool *reset) { #define AH_RX_STOP_DMA_TIMEOUT 10000 /* usec */ struct ath_common *common = ath9k_hw_common(ah); - u32 mac_status, last_mac_status = 0; +/* u32 mac_status, last_mac_status = 0;*/ + u32 mac_status = 0, last_mac_status = 0; int i; + ath_err(common, + "ath9k-mac.c ath9k_hw_stopdmarecv initial DMA started to stop in %d ms AR_CR=0x%08x AR_DIAG_SW=0x%08x DMADBG_7=0x%08x reset=%d\n", + AH_RX_STOP_DMA_TIMEOUT / 1000, + REG_READ(ah, AR_CR), + REG_READ(ah, AR_DIAG_SW), + REG_READ(ah, AR_DMADBG_7),reset); /* Enable access to the DMA observation bus */ REG_WRITE(ah, AR_MACMISC, @@ -712,6 +737,7 @@ bool ath9k_hw_stopdmarecv(struct ath_hw *ah, bool *reset) if (!AR_SREV_9300_20_OR_LATER(ah)) { mac_status = REG_READ(ah, AR_DMADBG_7) & 0x7f0; if (mac_status == 0x1c0 && mac_status == last_mac_status) { + /* if (mac_status == 0x020 && mac_status == last_mac_status) {*/ *reset = true; break; } @@ -723,14 +749,39 @@ bool ath9k_hw_stopdmarecv(struct ath_hw *ah, bool *reset) } if (i == 0) { - ath_err(common, - "DMA failed to stop in %d ms AR_CR=0x%08x AR_DIAG_SW=0x%08x DMADBG_7=0x%08x\n", - AH_RX_STOP_DMA_TIMEOUT / 1000, - REG_READ(ah, AR_CR), - REG_READ(ah, AR_DIAG_SW), - REG_READ(ah, AR_DMADBG_7)); + if (!AR_SREV_9300_20_OR_LATER(ah) && + (mac_status & 0x700) == 0) { + /* + * DMA is idle but the MAC is still stuck + * processing events + */ + ath_err(common, + "ath9k-mac.c ath9k_hw_stopdmarecv final DMA is idle but MAC is stuck AR_CR=0x%08x AR_DIAG_SW=0x%08x DMADBG_7=0x%08x reset=%d\n", + AH_RX_STOP_DMA_TIMEOUT / 1000, + REG_READ(ah, AR_CR), + REG_READ(ah, AR_DIAG_SW), + REG_READ(ah, AR_DMADBG_7),reset); + + *reset = true; + return true; + } + + ath_err(common, + "ath9k-mac.c ath9k_hw_stopdmarecv final DMA failed to go low in %d ms AR_CR=0x%08x AR_DIAG_SW=0x%08x DMADBG_7=0x%08x reset=%d\n", + AH_RX_STOP_DMA_TIMEOUT / 1000, + REG_READ(ah, AR_CR), + REG_READ(ah, AR_DIAG_SW), + REG_READ(ah, AR_DMADBG_7),reset); + return false; } else { + ath_err(common, + "ath9k-mac.c ath9k_hw_stopdmarecv final DMA stopped in %d ms AR_CR=0x%08x AR_DIAG_SW=0x%08x DMADBG_7=0x%08x reset=%d, i=%d\n", + AH_RX_STOP_DMA_TIMEOUT / 1000, + REG_READ(ah, AR_CR), + REG_READ(ah, AR_DIAG_SW), + REG_READ(ah, AR_DMADBG_7),reset,i); + return true; }
I forgot to mention if I clear the .mozilla/firefox/<user>.default/saved-telemetry-pings/ directory, it usually seems to work slightly better.
This may also be contributing. I turn off IPv6.. which in the ifcfg file which set IPV6INIT=no It looks like you get 2 IPv6 addresses if you do something like: [root@daffodil network-scripts]# cat ifcfg-net HWADDR=88:00:00:BB:11:EE ESSID="net" MODE=Managed KEY_MGMT=WPA-PSK TYPE=Wireless BOOTPROTO=dhcp DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=no IPV6_AUTOCONF=no IPV6_DEFROUTE=no IPV6_FAILURE_FATAL=no NAME=omalleynet UUID=f7348ae1-32e4-443f-9f52-f67cc96100d6 ONBOOT=yes IPV6_PEERDNS=no IPV6_PEERROUTES=no PEERDNS=yes PEERROUTES=yes [root@daffodil network-scripts]# [root@daffodil network-scripts]# ifconfig wlp2s0 wlp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.186 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 2602:306:c47e:7580:76de:2bff:feb1:3e1 prefixlen 64 scopeid 0x0<global> inet6 fe80::76de:2bff:feb1:3e1 prefixlen 64 scopeid 0x20<link> ether 74:de:2b:b1:03:e1 txqueuelen 1000 (Ethernet) RX packets 2567 bytes 613332 (598.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1302 bytes 211294 (206.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 [root@daffodil network-scripts]#
I downgraded to stock 4.2.3-300.fc23.x86_64 and it is still very erratic. anywhere from 0-10 minutes of network before it crashes.
The symptoms subside to some degree IF you open up an ssh session with keepalive set to 60 seconds.
It was fairly good, I think 1 reboot in 4 days.. The wireless router reset and reconnected without any issues. However, after the last update of: alsa-lib.x86_64 1.1.1-1.fc23 alsa-plugins-pulseaudio.x86_64 1.1.1-1.fc23 alsa-utils.x86_64 1.1.1-1.fc23 cups-filters.x86_64 1.8.3-1.fc23 cups-filters-libs.x86_64 1.8.3-1.fc23 grilo-plugins.x86_64 0.2.17-2.fc23 java-1.8.0-openjdk-headless.x86_64 1:1.8.0.77-1.b03.fc23 javapackages-tools.noarch 4.6.0-8.fc23 kexec-tools.x86_64 2.0.10-10.fc23 libipa_hbac.x86_64 1.13.3-6.fc23 libsss_autofs.x86_64 1.13.3-6.fc23 libsss_idmap.x86_64 1.13.3-6.fc23 libsss_nss_idmap.x86_64 1.13.3-6.fc23 libsss_sudo.x86_64 1.13.3-6.fc23 man-pages.noarch 4.00-7.fc23 mock.noarch 1.2.17-1.fc23 nmap-ncat.x86_64 2:7.12-1.fc23 python3-javapackages.noarch 4.6.0-8.fc23 python3-sssdconfig.noarch 1.13.3-6.fc23 sssd.x86_64 1.13.3-6.fc23 sssd-ad.x86_64 1.13.3-6.fc23 sssd-client.x86_64 1.13.3-6.fc23 sssd-common.x86_64 1.13.3-6.fc23 sssd-common-pac.x86_64 1.13.3-6.fc23 sssd-ipa.x86_64 1.13.3-6.fc23 sssd-krb5.x86_64 1.13.3-6.fc23 sssd-krb5-common.x86_64 1.13.3-6.fc23 sssd-ldap.x86_64 1.13.3-6.fc23 sssd-proxy.x86_64 1.13.3-6.fc23 systemtap.x86_64 3.0-2.fc23 systemtap-client.x86_64 3.0-2.fc23 systemtap-devel.x86_64 3.0-2.fc23 systemtap-runtime.x86_64 3.0-2.fc23 systemtap-sdt-devel.x86_64 3.0-2.fc23 It happened again right after the reboot after the installation. Even though I had an ssh window open. It was about 3 minutes... I will include the syslog.txt which is the bootlog for the session since it is relatively short and I have debugging on. The problem usually starts with: Apr 03 15:39:49 daffodil kernel: ath: phy0: Failed to stop TX DMA, queues=0x00a!
Created attachment 1143107 [details] system log
It might be a red herring, but given I needed to reboot 4 times in a row to get the file uploaded. I looked and gss-proxy was a service that I am pretty sure I had previously disabled, and may have been re-enabled during the update. (the sssd stuff?) I disabled it again, and I was least online long enough to upload the syslog, and post this.
Created attachment 1144429 [details] syslog from 4.5-302rc2
I upgraded to the F24 kernel today, 4.5.0-302.fc23.x86_64+debug, It is still happening. So I attached a complete log file.
Created attachment 1145428 [details] crash log from 4.5.0-302.fc23 This is the crash from the stock f23 kernel after the last update. I tried to unload and reload the kernel module (both successful so some improvement), but I was unable to get the network back up and running.
Created attachment 1146554 [details] another crash log. The incidence has dropped but it is still happening. The last update was: GeoIP-GeoLite-data.noarch 2016.04-1.fc23 elfutils.x86_64 0.166-1.fc23 elfutils-default-yama-scope.noarch 0.166-1.fc23 elfutils-devel.x86_64 0.166-1.fc23 elfutils-libelf.x86_64 0.166-1.fc23 elfutils-libelf-devel.x86_64 0.166-1.fc23 elfutils-libs.x86_64 0.166-1.fc23 krb5-devel.x86_64 1.14.1-5.fc23 krb5-libs.x86_64 1.14.1-5.fc23 krb5-workstation.x86_64 1.14.1-5.fc23 libatomic_ops.x86_64 7.4.2-9.fc23 libqb.x86_64 1.0-1.fc23 ntfs-3g.x86_64 2:2016.2.22-1.fc23 ntfsprogs.x86_64 2:2016.2.22-1.fc23 setroubleshoot-plugins.noarch 3.3.3-1.fc23 xen-libs.x86_64 4.5.3-1.fc23 xen-licenses.x86_64 4.5.3-1.fc23 xorg-x11-drv-wacom.x86_64 0.30.0-4.fc23
Created attachment 1146557 [details] another crash log 2.. This was a crash immediately prior to the last one. I mixed up the order. It didn't take long for the boot in this log to crash the network stack. I think I rebooted once yesterday, and zero times the day before.
This is still happening. It hasn't happened with a USB wireless adapter (yet).
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
It disappeared with the upgrade to F25.
Still present in Fedora 26 on an acer laptop after resuming from suspension. It doesn't happen everytime I resume, but happens very often. I can't connect to any network, NetworkManager seems to be scanning but doesn't find anything. The journal logs this: Jul 17 19:21:41 localhost.localdomain kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jul 17 19:21:42 localhost.localdomain wpa_supplicant[1108]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=00:22:75:22:5e:24 reason=4 locally_generated=1 Jul 17 19:21:42 localhost.localdomain kernel: ath: phy0: Chip reset failed Jul 17 19:21:42 localhost.localdomain kernel: ath: phy0: Unable to reset channel, reset status -22 Jul 17 19:21:42 localhost.localdomain NetworkManager[1124]: <warn> [1500312102.1073] sup-iface[0x56411d668530,wlp3s0]: connection disconnected (reason -4) Jul 17 19:21:42 localhost.localdomain NetworkManager[1124]: <info> [1500312102.1256] device (wlp3s0): supplicant interface state: completed -> disconnected Jul 17 19:21:42 localhost.localdomain wpa_supplicant[1108]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Jul 17 19:21:42 localhost.localdomain wpa_supplicant[1108]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=ES Jul 17 19:21:42 localhost.localdomain kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jul 17 19:21:42 localhost.localdomain NetworkManager[1124]: <info> [1500312102.4130] device (wlp3s0): supplicant interface state: disconnected -> scanning Jul 17 19:21:42 localhost.localdomain kernel: ath: phy0: Chip reset failed Jul 17 19:21:42 localhost.localdomain kernel: ath: phy0: Unable to reset channel, reset status -22 Jul 17 19:21:42 localhost.localdomain kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jul 17 19:21:42 localhost.localdomain kernel: ath: phy0: Chip reset failed Jul 17 19:21:42 localhost.localdomain kernel: ath: phy0: Unable to reset channel, reset status -22 Jul 17 19:21:42 localhost.localdomain kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jul 17 19:21:42 localhost.localdomain kernel: ath: phy0: Chip reset failed Jul 17 19:21:42 localhost.localdomain kernel: ath: phy0: Unable to reset channel, reset status -22 Jul 17 19:21:42 localhost.localdomain systemd-logind[1088]: Lid closed. Jul 17 19:21:42 localhost.localdomain systemd-logind[1088]: Suspending... Jul 17 19:21:42 localhost.localdomain NetworkManager[1124]: <info> [1500312102.8285] manager: sleep requested (sleeping: no enabled: yes) Jul 17 19:21:42 localhost.localdomain NetworkManager[1124]: <info> [1500312102.8285] manager: sleeping... Jul 17 19:21:42 localhost.localdomain NetworkManager[1124]: <info> [1500312102.8287] device (em1): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37] Jul 17 19:21:42 localhost.localdomain gnome-shell[1359]: Screen lock is locked down, not locking Jul 17 19:21:42 localhost.localdomain org.gnome.Shell.desktop[1359]: Window manager warning: Failed to set power save mode for output LVDS-1: Permission denied Jul 17 19:21:42 localhost.localdomain kernel: pci_bus 0000:02: Allocating resources Jul 17 19:21:42 localhost.localdomain kernel: pci_bus 0000:03: Allocating resources Jul 17 19:21:42 localhost.localdomain kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff Jul 17 19:21:43 localhost.localdomain kernel: ath: phy0: Chip reset failed Jul 17 19:21:43 localhost.localdomain kernel: ath: phy0: Unable to reset channel, reset status -22 Is the card failing to wake up? Kernel: 4.11.9-300.fc26.x86_64 Driver: ath9k Wifi card: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) (rev 01) http://svn.dd-wrt.com/ticket/2952
Still present in Fedora 29. dmesg: [ 4449.678378] ath: phy0: Chip reset failed [ 4449.678380] ath: phy0: Unable to reset channel, reset status -22 [ 4449.695783] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff [ 4449.979445] ath: phy0: Chip reset failed [ 4449.979447] ath: phy0: Unable to reset channel, reset status -22 [ 4449.996950] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff lspci -v 01:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) Subsystem: Lite-On Communications Inc Device 0802 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at d1400000 (64-bit, non-prefetchable) [size=512K] Expansion ROM at d1480000 [disabled] [size=64K] Capabilities: <access denied> Kernel driver in use: ath9k Kernel modules: ath9k uname -a: Linux librem 5.0.4-200.fc29.x86_64 #1 SMP Mon Mar 25 02:27:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
For what it is worth, my problem went away when I physically removed the wifi card and then reseated it. So this can result from a hardware problem.
Following the suggestion in the prior comment I took the back off my ancient netbook, found the wireless card and re-seated it, which at least for now has fixed the issue.