2068350 – Wifi: AR9485 Unstable after update

Bug 2068350 - Wifi: AR9485 Unstable after update

Summary: Wifi: AR9485 Unstable after update

Keywords:
Status:	CLOSED DUPLICATE of bug 2067108
Alias:	None
Product:	Fedora
Classification:	Fedora
Component:	kernel
Sub Component:
Version:	35
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	medium
Target Milestone:	---
Assignee:	Kernel Maintainer List
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2022-03-25 03:05 UTC by Platypus x86
Modified:	2022-03-25 13:01 UTC (History)
CC List:	19 users (show)
Fixed In Version:
Clone Of:
Environment:
Last Closed:	2022-03-25 13:01:47 UTC
Type:	Bug
Embargoed:
Dependent Products:

Attachments	(Terms of Use)
7. journalctl (94.57 KB, text/plain) 2022-03-25 03:05 UTC, Platypus x86	no flags	Details
View All

Description Platypus x86 2022-03-25 03:05:56 UTC

Created attachment 1868252 [details]
7. journalctl

Created attachment 1868252 [details]
7. journalctl

Hey guys!
Many thanks!

1. Please describe the problem:

Unstable Wifi AR9485 after last update. (3 or 5 days)
Wifi power was 60+% now is 49% or less never 60% again.

I make a fresh install. All was working fine!
Updated fc all instability came back again.

2. What is the Version-Release number of the kernel:

5.16.16-200.fc35.x86_64 #1 SMP PREEMPT Sat Mar 19 13:52:41 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

Works fine before update.


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Yes. sudo dnf update -y


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:


6. Are you running any modules that not shipped with directly Fedora's kernel?:
No

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

In Attachment

--------------8<---------------------------------
/var/log/messages

Mar 24 23:04:12 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-BEACON-LOSS
Mar 24 23:04:13 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-BEACON-LOSS
Mar 24 23:04:14 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-BEACON-LOSS
Mar 24 23:04:15 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-BEACON-LOSS
Mar 24 23:04:16 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-BEACON-LOSS
Mar 24 23:04:16 laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 24 23:04:17 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-BEACON-LOSS
Mar 24 23:04:18 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-BEACON-LOSS
Mar 24 23:04:19 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-BEACON-LOSS
Mar 24 23:04:20 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-BEACON-LOSS
Mar 24 23:04:21 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-BEACON-LOSS
Mar 24 23:04:21 laptop kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006100
Mar 24 23:04:21 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-DISCONNECTED bssid=83:9a:09:8f:06:84 reason=4 locally_generated=1
Mar 24 23:04:21 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Mar 24 23:04:21 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=BR
Mar 24 23:04:21 laptop NetworkManager[747]: <info>  [1648173861.7308] device (wlp4s0): supplicant interface state: completed -> disconnected
Mar 24 23:04:21 laptop NetworkManager[747]: <info>  [1648173861.7312] device (p2p-dev-wlp4s0): supplicant management interface state: completed -> disconnected
Mar 24 23:04:21 laptop NetworkManager[747]: <info>  [1648173861.8213] device (wlp4s0): supplicant interface state: disconnected -> scanning
Mar 24 23:04:21 laptop NetworkManager[747]: <info>  [1648173861.8214] device (p2p-dev-wlp4s0): supplicant management interface state: disconnected -> scanning
Mar 24 23:04:22 laptop wpa_supplicant[826]: wlp4s0: SME: Trying to authenticate with 83:9a:09:8f:06:84 (SSID='Aplan' freq=2452 MHz)
Mar 24 23:04:22 laptop kernel: wlp4s0: authenticate with 83:9a:09:8f:06:84
Mar 24 23:04:22 laptop kernel: wlp4s0: send auth to 83:9a:09:8f:06:84 (try 1/3)
Mar 24 23:04:22 laptop NetworkManager[747]: <info>  [1648173862.7810] device (wlp4s0): supplicant interface state: scanning -> authenticating
Mar 24 23:04:22 laptop NetworkManager[747]: <info>  [1648173862.7812] device (p2p-dev-wlp4s0): supplicant management interface state: scanning -> authenticating
Mar 24 23:04:22 laptop wpa_supplicant[826]: wlp4s0: Trying to associate with 83:9a:09:8f:06:84 (SSID='Aplan' freq=2452 MHz)
Mar 24 23:04:22 laptop kernel: wlp4s0: authenticated
Mar 24 23:04:22 laptop kernel: wlp4s0: associate with 83:9a:09:8f:06:84 (try 1/3)
Mar 24 23:04:22 laptop NetworkManager[747]: <info>  [1648173862.7976] device (wlp4s0): supplicant interface state: authenticating -> associating
Mar 24 23:04:22 laptop NetworkManager[747]: <info>  [1648173862.7978] device (p2p-dev-wlp4s0): supplicant management interface state: authenticating -> associating
Mar 24 23:04:22 laptop kernel: wlp4s0: RX AssocResp from 83:9a:09:8f:06:84 (capab=0x411 status=0 aid=5)
Mar 24 23:04:22 laptop kernel: wlp4s0: associated
Mar 24 23:04:22 laptop wpa_supplicant[826]: wlp4s0: Associated with 83:9a:09:8f:06:84
Mar 24 23:04:22 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Mar 24 23:04:22 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=BR
Mar 24 23:04:22 laptop NetworkManager[747]: <info>  [1648173862.8110] device (wlp4s0): supplicant interface state: associating -> associated
Mar 24 23:04:22 laptop NetworkManager[747]: <info>  [1648173862.8112] device (p2p-dev-wlp4s0): supplicant management interface state: associating -> associated
Mar 24 23:04:22 laptop NetworkManager[747]: <info>  [1648173862.8112] device (wlp4s0): DHCPv4 lease renewal requested
Mar 24 23:04:22 laptop NetworkManager[747]: <info>  [1648173862.8182] dhcp4 (wlp4s0): canceled DHCP transaction
Mar 24 23:04:22 laptop NetworkManager[747]: <info>  [1648173862.8183] dhcp4 (wlp4s0): state changed bound -> terminated
Mar 24 23:04:22 laptop NetworkManager[747]: <info>  [1648173862.8193] dhcp4 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
Mar 24 23:04:22 laptop NetworkManager[747]: <info>  [1648173862.8225] device (wlp4s0): supplicant interface state: associated -> 4way_handshake
Mar 24 23:04:22 laptop NetworkManager[747]: <info>  [1648173862.8226] device (p2p-dev-wlp4s0): supplicant management interface state: associated -> 4way_handshake
Mar 24 23:04:22 laptop wpa_supplicant[826]: wlp4s0: WPA: Key negotiation completed with 83:9a:09:8f:06:84 [PTK=CCMP GTK=CCMP]
Mar 24 23:04:22 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-CONNECTED - Connection to 83:9a:09:8f:06:84 completed [id=0 id_str=]
Mar 24 23:04:22 laptop NetworkManager[747]: <info>  [1648173862.8425] device (wlp4s0): supplicant interface state: 4way_handshake -> completed
Mar 24 23:04:22 laptop NetworkManager[747]: <info>  [1648173862.8430] device (p2p-dev-wlp4s0): supplicant management interface state: 4way_handshake -> completed
Mar 24 23:04:23 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-68 noise=-95 txrate=14400
Mar 24 23:04:24 laptop NetworkManager[747]: <info>  [1648173864.9832] dhcp4 (wlp4s0): state changed unknown -> bound, address=10.0.0.3
Mar 24 23:04:25 laptop systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 24 23:04:25 laptop systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 24 23:04:27 laptop systemsettings[3070]: qt.svg: Cannot open file ':/icons/kdeconnect/kdeconnect.svg', because: No such file or directory
Mar 24 23:04:27 laptop systemsettings[3070]: qt.svg: Cannot open file ':/icons/kdeconnect/kdeconnect.svg', because: No such file or directory
Mar 24 23:04:27 laptop plasmashell[1034]:    RemoteCommandsDbusInterface::canAddCommand
Mar 24 23:04:29 laptop systemsettings[3070]: org.kde.libkbolt: Failed to connect to Bolt manager DBus interface:
Mar 24 23:04:29 laptop systemsettings[3070]: QQmlEngine::setContextForObject(): Object already has a QQmlContext
Mar 24 23:04:33 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-BEACON-LOSS
Mar 24 23:04:34 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-BEACON-LOSS
Mar 24 23:04:35 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-BEACON-LOSS
Mar 24 23:04:35 laptop kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006100
Mar 24 23:04:35 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-DISCONNECTED bssid=83:9a:09:8f:06:84 reason=4 locally_generated=1
Mar 24 23:04:35 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Mar 24 23:04:35 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=BR
Mar 24 23:04:35 laptop NetworkManager[747]: <info>  [1648173875.7376] device (wlp4s0): supplicant interface state: completed -> disconnected
Mar 24 23:04:35 laptop NetworkManager[747]: <info>  [1648173875.7378] device (p2p-dev-wlp4s0): supplicant management interface state: completed -> disconnected
Mar 24 23:04:35 laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 24 23:04:35 laptop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 24 23:04:35 laptop NetworkManager[747]: <info>  [1648173875.8342] device (wlp4s0): supplicant interface state: disconnected -> scanning
Mar 24 23:04:35 laptop NetworkManager[747]: <info>  [1648173875.8343] device (p2p-dev-wlp4s0): supplicant management interface state: disconnected -> scanning
Mar 24 23:04:36 laptop wpa_supplicant[826]: wlp4s0: SME: Trying to authenticate with 83:9a:09:8f:06:84 (SSID='Aplan' freq=2452 MHz)
Mar 24 23:04:36 laptop kernel: wlp4s0: authenticate with 83:9a:09:8f:06:84
Mar 24 23:04:36 laptop kernel: wlp4s0: send auth to 83:9a:09:8f:06:84 (try 1/3)
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.7897] device (wlp4s0): supplicant interface state: scanning -> authenticating
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.7899] device (p2p-dev-wlp4s0): supplicant management interface state: scanning -> authenticating
Mar 24 23:04:36 laptop wpa_supplicant[826]: wlp4s0: Trying to associate with 83:9a:09:8f:06:84 (SSID='Aplan' freq=2452 MHz)
Mar 24 23:04:36 laptop kernel: wlp4s0: authenticated
Mar 24 23:04:36 laptop kernel: wlp4s0: associate with 83:9a:09:8f:06:84 (try 1/3)
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.8010] device (wlp4s0): supplicant interface state: authenticating -> associating
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.8012] device (p2p-dev-wlp4s0): supplicant management interface state: authenticating -> associating
Mar 24 23:04:36 laptop kernel: wlp4s0: RX AssocResp from 83:9a:09:8f:06:84 (capab=0x411 status=0 aid=5)
Mar 24 23:04:36 laptop kernel: wlp4s0: associated
Mar 24 23:04:36 laptop wpa_supplicant[826]: wlp4s0: Associated with 83:9a:09:8f:06:84
Mar 24 23:04:36 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Mar 24 23:04:36 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=BR
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.8131] device (wlp4s0): supplicant interface state: associating -> associated
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.8133] device (p2p-dev-wlp4s0): supplicant management interface state: associating -> associated
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.8134] device (wlp4s0): DHCPv4 lease renewal requested
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.8234] dhcp4 (wlp4s0): canceled DHCP transaction
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.8235] dhcp4 (wlp4s0): state changed bound -> terminated
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.8248] dhcp4 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
Mar 24 23:04:36 laptop wpa_supplicant[826]: wlp4s0: WPA: Key negotiation completed with 83:9a:09:8f:06:84 [PTK=CCMP GTK=CCMP]
Mar 24 23:04:36 laptop wpa_supplicant[826]: wlp4s0: CTRL-EVENT-CONNECTED - Connection to 83:9a:09:8f:06:84 completed [id=0 id_str=]
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.8570] device (wlp4s0): supplicant interface state: associated -> 4way_handshake
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.8571] device (p2p-dev-wlp4s0): supplicant management interface state: associated -> 4way_handshake
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.8573] device (wlp4s0): supplicant interface state: 4way_handshake -> completed
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.8578] device (p2p-dev-wlp4s0): supplicant management interface state: 4way_handshake -> completed
Mar 24 23:04:36 laptop NetworkManager[747]: <info>  [1648173876.9271] dhcp4 (wlp4s0): state changed unknown -> bound, address=10.0.0.3

Comment 1 Justin M. Forbes 2022-03-25 13:01:47 UTC


*** This bug has been marked as a duplicate of bug 2067108 ***

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