Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1a3b:2231] network-manager crashes: "NetworkManager needs to be running"

[Mahdi Gerami]

Hi. Sometimes network-manager crashes and I can't connect to any network. Restarting the network manager service via terminal hangs and even restarting the OS hangs and I have to force shutdown via power button.

When I open settings > Wi-Fi it says: "Oops, something has gone wrong. Please contact your software vendor. NetworkManager needs to be running".

I'm not facing the problem right now as I just restarted my laptop so if there's any information that I need to gather while this problem is happening, let me know. Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-lowlatency 5.4.44
Uname: Linux 5.4.0-42-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 23 14:07:57 2020
InstallationDate: Installed on 2020-06-20 (33 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 20600
 169.254.0.0/16 dev wlp2s0 scope link metric 1000
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.36 metric 600
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH
 wlp2s0 wifi connected limited limited /org/freedesktop/NetworkManager/Devices/2 neverlookaway 7b44595b-b6bc-4add-9873-a7af7393c65d /org/freedesktop/NetworkManager/ActiveConnection/1
 p2p-dev-wlp2s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- --
 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- --
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.22.10 connected (site only) started limited enabled enabled enabled enabled enabled

[Sebastien Bacher (seb128)]

Thank you for your bug report. Do you have specific steps that trigger the issue? Could you add the 'journalctl -b <n>' from a session where you got the issue (n = 1 probably if you restarted once since you got the issue)

Could you also try to get a backtrace by following https://wiki.ubuntu.com/Backtrace ?

The apport service should catch those issues but doesn't at the moment because of bug #1870060 , one workaround is to comment the ProtectSystem line from the systemd .service and restart, then apport should catch the segfault

[Tarik Yigit (ygttrk)]

Same issue occurs in my Ubuntu 20.04 on my PC, too. This doesn't happen in Windows system installed on the same PC. It just happens in every one or two hours without any specific steps. The only way to connect to the network is by hard resetting the machince which is very annoying especially when you are in the middle of something.

[Mahdi Gerami (mahdi-gerami77)]

So I think this is the journalctl from the time it crashed. These lines caught my eyes:

Jul 23 14:52:40 creative-machine kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x00036044: -110

Jul 23 14:52:41 creative-machine kernel: ath10k_pci 0000:02:00.0: firmware crashed! (guid a3417396-44ed-4633-81d1-fc662aad62b4)

[Sebastien Bacher (seb128)]

Thanks, the log extract you copied suggests it's a firware or driver issue, reassign to linux

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1888648

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[You-Sheng Yang (vicamo)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest kernel [0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed”, and attach dmesg.

Thanks in advance.

[0]: https://kernel.ubuntu.com/~kernel-ppa/mainline/

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]