dhclient then ath10k firmware crashes

Bug #1869078 reported by thedoctar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
isc-dhcp (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I had to restart so not sure if automatically generated debug-info is relevant.

In my journalctl I get this error:
Mar 25 21:17:10 dhclient[29542]: For info, please visit https://www.isc.org/software/dhcp/
Mar 25 21:17:10 dhclient[29542]:
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 45: numeric minute expected.
Mar 25 21:17:10 dhclient[29542]: rebind 3 2020/03/25 18:lease
Mar 25 21:17:10 dhclient[29542]: ^
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 45: semicolon expected.
Mar 25 21:17:10 dhclient[29542]: rebind 3 2020/03/25 18:lease {
Mar 25 21:17:10 dhclient[29542]: ^
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 79: expecting numeric value.
Mar 25 21:17:10 dhclient[29542]: option routers 192.168.0lease
Mar 25 21:17:10 dhclient[29542]: ^
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 142: unterminated lease declaration.
...
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: firmware crashed! (guid 9bfed658-d8c1-48ad-9172-538c9219d4df)
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: failed to get memcpy hi address for firmware address 4: -16
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: failed to read firmware dump area: -16
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: Copy Engine register dump:
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci 0000:3a:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295
Mar 25 21:17:11 kernel: ath10k_pci 0000:3a:00.0: failed to receive control response completion, polling..
Mar 25 21:17:11 kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0x00000001 at 0x00034430: -110
Mar 25 21:17:11 kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x00034444: -110
Mar 25 21:17:11 kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0x0000001e at 0x00034430: -110
Mar 25 21:17:11 kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0x00000001 at 0x00034830: -110
Mar 25 21:17:11 kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0x00000001 at 0x00035430: -110
Mar 25 21:17:11 kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x00035444: -110
Mar 25 21:17:11 kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0x0000001e at 0x00035430: -110
Mar 25 21:17:12 kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0x0000001e at 0x00034830: -110
Mar 25 21:17:13 kernel: ath10k_pci 0000:3a:00.0: ctl_resp never came in (-110)
Mar 25 21:17:13 kernel: ath10k_pci 0000:3a:00.0: failed to connect to HTC: -110

Full debug log attached.

My system froze. I was watching a move and the video stopped, audio skipped. Hence why there are alsa complaints in the debug.

The ath10k firmware crashed and I couldn't reload.

Ubuntu 18.04.4 LTS

Linux albert-XPS-13-9360 5.5.0-050500-generic #202001262030 SMP Mon Jan 27 01:33:36 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  *-network
       description: Wireless interface
       product: QCA6174 802.11ac Wireless Network Adapter
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:3a:00.0
       logical name: wlp58s0
       version: 32
       serial: 9c:b6:d0:d4:9b:33
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=ath10k_pci driverversion=5.5.0-050500-generic firmware=WLAN.RM.4.4.1-00140-QCARMSWPZ-1 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:135 memory:dc000000-dc1fffff

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: isc-dhcp-client 4.3.5-3ubuntu7.1
Uname: Linux 5.5.0-050500-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.12
Architecture: amd64
Date: Wed Mar 25 21:39:20 2020
ExecutablePath: /sbin/dhclient
InstallationDate: Installed on 2017-02-26 (1123 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcAttrCurrent: /sbin/dhclient (enforce)
ProcEnviron:
 LANG=en_AU.UTF-8
 TERM=xterm-256color
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 SHELL=/bin/bash
SourcePackage: isc-dhcp
UpgradeStatus: Upgraded to bionic on 2018-10-06 (536 days ago)

Revision history for this message
thedoctar (thedoctar) wrote :
description: updated
Revision history for this message
thedoctar (thedoctar) wrote :

It seems to have disappeared when I updated dhclient to 4.4.2

Changed in isc-dhcp (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.