After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 797067 - ath10k_pci firmware crashes after shutdown of networking
ath10k_pci firmware crashes after shutdown of networking
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
unspecified
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2018-09-02 17:46 UTC by Leon
Modified: 2020-11-12 14:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
kern.log (4.42 KB, text/x-log)
2018-09-02 17:46 UTC, Leon
Details
NetworkManager.log (2.29 KB, text/x-log)
2018-09-03 19:41 UTC, Leon
Details

Description Leon 2018-09-02 17:46:45 UTC
Created attachment 373537 [details]
kern.log

Hi,

when I try to stop the networking, my system becomes unstable and then finally crashes.
This happens automatically, when I try to set my PC to "Standby" (Suspend to RAM).

I can reproduce the behaviour with this command:
nmcli networking off

in /var/log/kern.log i find these lines:
[ 4724.921076] wlp2s0: deauthenticating from 90:f6:52:27:75:64 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 4724.926122] ath10k_pci 0000:02:00.0: firmware crashed! (guid 2cb5e277-542a-4dc3-93ed-02e69875cdf7)
[ 4724.926131] ath10k_pci 0000:02:00.0: qca6174 hw2.1 target 0x05010000 chip_id 0x003405ff sub 11ad:0804

When I use the following command, the firmware does not crash:
wpa_cli -i wlp2s0 logoff

My kernel version:
4.18.5-041805-generic #201808241320 SMP Fri Aug 24 13:22:12 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

sudo ethtool -i wlp2s0 gives this info:
driver: ath10k_pci
version: 4.18.5-041805-generic
firmware-version: SW_RM.1.1.1-00157-QCARMSWPZ-1
expansion-rom-version: 
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

lspci -nn gives this info:
02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 20)
Comment 1 Thomas Haller 2018-09-03 15:08:42 UTC
A crash of the firmware/kernel is usually not a bug in NetworkManager.

I think you should report this bug to kernel; possibly to your distribution which provided you with that particular kernel version.

also, the bug report does not contain the logfile of NetworkManager, to understand what NetworkManager did at the exact moment to trigger the issue.
Comment 2 Leon 2018-09-03 19:41:08 UTC
Created attachment 373540 [details]
NetworkManager.log
Comment 3 Leon 2018-09-03 19:45:12 UTC
Hi Thomas,
I have read here:
https://wireless.wiki.kernel.org/en/users/documentation/reporting_bugs
that I should report the bug here, because it does not happen, when I use the wpa_cli command. At least I understood so, because wpa_cli is an interface to wpa_supplicant... ?

Can you see anything interesting in the NetworkManager-Logfile?
Comment 4 Thomas Haller 2018-09-04 08:13:35 UTC
(In reply to Leon from comment #3)
> Hi Thomas,
> I have read here:
> https://wireless.wiki.kernel.org/en/users/documentation/reporting_bugs
> that I should report the bug here, because it does not happen, when I use
> the wpa_cli command. At least I understood so, because wpa_cli is an
> interface to wpa_supplicant... ?

If a driver/firmware crashes, it's a bug in the driver/firmware. It does not matter that some user-space tools exhibit the bug while others don't.



> Can you see anything interesting in the NetworkManager-Logfile?

Thank you! But the logfile is not interleaved with messages from kernel, so it's unclear at which exact point the issue happens. Also, NetworkManager logs with <info> level usually are unfortunately not helpful for debugging. See comments at https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf for how to enable level=TRACE.

Anyway, the crash seems related to setting the radio killswitch, which is also what `nmcli networking off` does.
Comment 5 André Klapper 2020-11-12 14:25:16 UTC
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).