Ubuntu
linux package

Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic on Dell XPS 13 9370

Bug #1807974 reported by Aaron Whitehouse on 2018-12-11

132

This bug affects 27 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

I have a Dell XPS 13 9370 developer edition (Ubuntu version) running Cosmic. A handful of times per day, my wireless stops working ("?" appears in the icon in Network Manager). Turning wireless off and then on again, or suspending and waking the machine up, makes the wireless work again.

dmesg output is as follows:

$ dmesg | grep ath10k

[ 6646.268929] ath10k_pci 0000:02:00.0: firmware crashed! (guid 6317c652-4817-4fdd-b6d7-c7b8336e493f)
[ 6646.268982] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[ 6646.268990] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 6646.270369] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 6646.271379] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3
[ 6646.271393] ath10k_pci 0000:02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 6646.283333] ath10k_pci 0000:02:00.0: failed to get memcpy hi address for firmware address 4: -16
[ 6646.283336] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -16
[ 6646.283339] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[ 6646.283348] ath10k_pci 0000:02:00.0: [00]: 0x00034400 14 14 3 3
[ 6646.283357] ath10k_pci 0000:02:00.0: [01]: 0x00034800 29 29 106 107
[ 6646.283365] ath10k_pci 0000:02:00.0: [02]: 0x00034c00 20 19 18 19
[ 6646.283374] ath10k_pci 0000:02:00.0: [03]: 0x00035000 8 8 10 8
[ 6646.283386] ath10k_pci 0000:02:00.0: [04]: 0x00035400 2763 2763 167 103
[ 6646.283394] ath10k_pci 0000:02:00.0: [05]: 0x00035800 0 0 64 0
[ 6646.283402] ath10k_pci 0000:02:00.0: [06]: 0x00035c00 0 0 6 6
[ 6646.283412] ath10k_pci 0000:02:00.0: [07]: 0x00036000 0 1 0 1
[ 6646.301351] ath10k_pci 0000:02:00.0: failed to read hi_board_data address: -28
[ 6647.126841] ath10k_pci 0000:02:00.0: Unknown eventid: 118809
[ 6647.129850] ath10k_pci 0000:02:00.0: Unknown eventid: 90118
[ 6647.239340] ath10k_pci 0000:02:00.0: device successfully recovered

[17641.847345] ath10k_pci 0000:02:00.0: firmware crashed! (guid 03393f2f-0ce1-4017-b711-40dd14f2ec11)
[17641.847363] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[17641.847367] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[17641.848065] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[17641.848585] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3
[17641.848593] ath10k_pci 0000:02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[17641.860559] ath10k_pci 0000:02:00.0: failed to get memcpy hi address for firmware address 4: -16
[17641.860587] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -16
[17641.860595] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[17641.860611] ath10k_pci 0000:02:00.0: [00]: 0x00034400 14 14 3 3
[17641.860624] ath10k_pci 0000:02:00.0: [01]: 0x00034800 6 6 243 244
[17641.860639] ath10k_pci 0000:02:00.0: [02]: 0x00034c00 53 52 51 52
[17641.860656] ath10k_pci 0000:02:00.0: [03]: 0x00035000 5 5 7 5
[17641.860669] ath10k_pci 0000:02:00.0: [04]: 0x00035400 1231 1231 169 105
[17641.860681] ath10k_pci 0000:02:00.0: [05]: 0x00035800 0 0 64 0
[17641.860693] ath10k_pci 0000:02:00.0: [06]: 0x00035c00 0 0 30 30
[17641.860706] ath10k_pci 0000:02:00.0: [07]: 0x00036000 0 1 0 1
[17641.890915] ath10k_pci 0000:02:00.0: failed to read hi_board_data address: -28
[17642.714052] ath10k_pci 0000:02:00.0: Unknown eventid: 118809
[17642.717154] ath10k_pci 0000:02:00.0: Unknown eventid: 90118
[17642.835601] ath10k_pci 0000:02:00.0: device successfully recovered
[17894.571696] ath10k_pci 0000:02:00.0: Unknown eventid: 118809
[17894.574764] ath10k_pci 0000:02:00.0: Unknown eventid: 90118

I do not recall having any wireless issues before I upgraded (when this machine was running Bionic).

Bug #1730331 - ath10k_pci: firmware crashed!
Bug #1627474 - ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a) [16.10]
could be related, but appear to be related to earlier releases, whereas my issue has appeared/become much worse on Cosmic.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-11-generic 4.18.0-11.12
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: aaron-work 3476 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 11 14:21:44 2018
EcryptfsInUse: Yes
HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1
InstallationDate: Installed on 2018-09-04 (98 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9370
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=/dev/mapper/ubuntu-vg-swap_1 vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.18.0-11-generic N/A
linux-backports-modules-4.18.0-11-generic N/A
linux-firmware 1.175.1
SourcePackage: linux
UpgradeStatus: Upgraded to cosmic on 2018-10-26 (45 days ago)
WifiSyslog:

dmi.bios.date: 08/09/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.name: 0F6P3V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.

Tags:

Revision history for this message

Aaron Whitehouse (aaron-whitehouse) wrote on 2018-12-11:

AlsaInfo.txt Edit (48.2 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (468 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (254.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.6 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (503 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (11.7 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (10.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (115 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (6.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (10.5 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (42.1 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (112 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (210.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2018-12-11: Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2018-12-13: Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic

Was the network is under heavy load, or in idle?

Changed in linux (Ubuntu):
assignee:	nobody → Kai-Heng Feng (kaihengfeng)

Revision history for this message

Aaron Whitehouse (aaron-whitehouse) wrote on 2018-12-18:

Normally (maybe always?) it is when the network is idle. Thanks.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2018-12-19:

The firmware for this device got updated recently [1].
Please copy binary blobs in [2] to the same relative path under /lib/firmwares/.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a87eb5f7bac0f70ade57da57d9126d14eee12336

[2] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ath10k/QCA6174/hw3.0

Revision history for this message

Aaron Whitehouse (aaron-whitehouse) wrote on 2019-01-07:

Done, thanks Kai-Heng. How can I check I'm using the new versions?

$ dmesg | grep ath10k
[ 15.152725] ath10k_pci 0000:02:00.0: enabling device (0000 -> 0002)
[ 15.154816] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 15.436782] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[ 15.436784] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 15.437201] ath10k_pci 0000:02:00.0: firmware ver RM.4.4.1.c2-00057-QCARMSWP-1 api 6 features wowlan,ignore-otp,no-4addr-pad,raw-mode crc32 e061250a
[ 15.502002] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3
[ 16.081468] ath10k_pci 0000:02:00.0: Unknown eventid: 118809
[ 16.084029] ath10k_pci 0000:02:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 16.176519] ath10k_pci 0000:02:00.0 wlp2s0: renamed from wlan0
[ 19.218623] ath10k_pci 0000:02:00.0: Unknown eventid: 118809

I will let you know how I get on. Even before loading the new firmware I am seeing this issue far less frequently (only twice so far today) since I changed s2idle to deep sleep (Bug #1808957), so I suspect it does relate to idle/power saving.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2019-01-07:

Do you mean the issue happen less frequently when using S3 instead of S2Idle? I thought this should be the other way around.

Revision history for this message

Aaron Whitehouse (aaron-whitehouse) wrote on 2019-01-07:

Correct. Since I have been using Deep instead of S2Idle I have seen the issue less -- though it has only been a couple of days as I was not using this machine over the holidays. Even when it does break, Deep suspending and resuming the machine brings the wireless back up and working.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2019-01-08:

Please attach output of `sudo lspci -vvv -s 02:00.0`.
I think I've seen several platforms that requires to tweak PCI ASPM bits.

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2019-01-08:

#10

According to [1], new firmware can fix the issue.

[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799988/comments/42

Revision history for this message

Aaron Whitehouse (aaron-whitehouse) wrote on 2019-01-08:

#11

Download full text (3.6 KiB)

Using the firmware from Comment #5 above stopped the wireless and my my Bluetooth mouse from working, so I have reverted it to the standard Ubuntu version.

sudo lspci -vvv -s 02:00.0 gives:

02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 135
Region 0: Memory at dc000000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Power Management version 3
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
  Address: fee00418 Data: 0000
  Masking: 000000fe Pending: 00000000
Capabilities: [70] Express (v2) Endpoint, MSI 00
  DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
   ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
   MaxPayload 256 bytes, MaxReadReq 512 bytes
  DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
  LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us
   ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
  LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
   ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
  DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, OBFF Via message
  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled
  LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
    Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
    Compliance De-emphasis: -6dB
  LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
    EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v2] Advanced Error Reporting
  UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
  CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
  CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
  AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
Capabilities: [148 v1] Virtual Channel
  Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
  Arb: Fixed- WRR32- WRR64- WRR128-
  Ctrl: ArbSelect=Fixed
  Status: InProgress-
  VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
   Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
   Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
   Status: NegoPending- InProgress-
Capabilities: [168 v1] D...

Using the firmware from Comment #5 above stopped the wireless and my my Bluetooth mouse from working, so I have reverted it to the standard Ubuntu version.

sudo lspci -vvv -s 02:00.0 gives:

02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
	Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 135
	Region 0: Memory at dc000000 (64-bit, non-prefetchable) [size=2M]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
		Address: fee00418  Data: 0000
		Masking: 000000fe  Pending: 00000000
	Capabilities: [70] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, OBFF Via message
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
	Capabilities: [148 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [168 v1] Device Serial Number 00-00-00-00-00-00-00-00
	Capabilities: [178 v1] Latency Tolerance Reporting
		Max snoop latency: 3145728ns
		Max no snoop latency: 3145728ns
	Capabilities: [180 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=50us PortTPowerOnTime=10us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=0us LTR1.2_Threshold=163840ns
		L1SubCtl2: T_PwrOn=44us
	Kernel driver in use: ath10k_pci
	Kernel modules: ath10k_pci

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2019-01-11:

#12

I think the firmware is the same, so only the board-2.bin file needs to be copied.

I am still seeing the issue with new board-2.bin.

Revision history for this message

brian.mcclr (brian-mcclr) wrote on 2019-02-09:

#13

Any updates or progress being made on this?

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2019-03-21:

#14

Possible to try Cosmic's firmware + Bionic's v4.15 kernel? Let's find the which package introduces the regression first.

Kai-Heng Feng (kaihengfeng) on 2019-07-05

Changed in linux (Ubuntu):
assignee:	Kai-Heng Feng (kaihengfeng) → nobody

Revision history for this message

Mike Meehan (mjmeehan) wrote on 2019-07-21:

#15

This also affects the Dell XPS 13 9380 and Disco 19.04. The issue occurs after resume from sleep.
Firmware version RM.4.4.1.c2-00057-QCARMSWP-1 (latest from the ath git repo)
Kernel version 5.0.0-20-generic
dmesg output:
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: failed to read device register, device is gone
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: firmware crashed! (guid a6019044-1af6-47d3-b950-770d4257c7cb)
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: firmware ver RM.4.4.1.c2-00057-QCARMSWP-1 api 6 features wowlan,ignore-otp,no-4addr-pad,raw-mode crc32 e061250a
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -28
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: failed to reset chip: -5
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: Could not init hif: -5

This also affects the Dell XPS 13 9380 and Disco 19.04. The issue occurs after resume from sleep. 
Firmware version RM.4.4.1.c2-00057-QCARMSWP-1 (latest from the ath git repo)
Kernel version 5.0.0-20-generic
dmesg output:
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: failed to read device register, device is gone
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: firmware crashed! (guid a6019044-1af6-47d3-b950-770d4257c7cb)
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: firmware ver RM.4.4.1.c2-00057-QCARMSWP-1 api 6 features wowlan,ignore-otp,no-4addr-pad,raw-mode crc32 e061250a
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -28
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: failed to reset chip: -5
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: Could not init hif: -5

Revision history for this message

Mike Meehan (mjmeehan) wrote on 2019-07-21:

#16

Ok, looks like I was still running an older firmware version. I upgraded by:

Checking out the ath10k firmware repo https://github.com/kvalo/ath10k-firmware.git
Copying the latest firmware for my card from ath10k-firmware/QCA6174/hw3.0/4.4.1.c3/firmware-6.bin_WLAN.RM.4.4.1.c3-00035
to /lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin
Rebooting
Now I'm on WLAN.RM.4.4.1.c3-00035

$ sudo ethtool -i wlp2s0
driver: ath10k_pci
version: 5.0.0-20-generic
firmware-version: WLAN.RM.4.4.1.c3-00035
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

Revision history for this message

Mike Meehan (mjmeehan) wrote on 2019-07-23:

#17

Broken with the latest firmware:

[Tue Jul 23 06:11:13 2019] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[Tue Jul 23 06:11:13 2019] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[Tue Jul 23 06:11:14 2019] ath10k_pci 0000:02:00.0: failed to read device register, device is gone
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: firmware crashed! (guid 34bd9ffb-d5be-41bc-ae93-acba18ad9b79)
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1.c3-00035 api 6 features wowlan,ignore-otp,no-4addr-pad,raw-mode,mfp crc32 ade47a0d
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: htt-ver 3.62 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -28
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295
[Tue Jul 23 06:11:15 2019] ath10k_pci 0000:02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295
[Tue Jul 23 06:11:16 2019] ath10k_pci 0000:02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295
[Tue Jul 23 06:11:16 2019] ath10k_pci 0000:02:00.0: failed to reset chip: -5
[Tue Jul 23 06:11:16 2019] ath10k_pci 0000:02:00.0: Could not init hif: -5

Broken with the latest firmware:

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2019-07-24:

#18

Mike,

Please attach full dmesg, thanks!

Brad Figg (brad-figg) on 2019-07-24

tags:

added: ubuntu-certified

Revision history for this message

TomaszChmielewski (mangoo-wpkg) wrote on 2019-08-19:

#19

This also affects Dell Precision 5520 running Ubuntu 19.04.

Rex Tsai (chihchun) on 2019-10-07

summary:

Wireless regularly breaking (ath10k firmware crashed!) after upgrade to
- Cosmic
+ Cosmic on Dell XPS 13 9370

Revision history for this message

Loris Zinsou (nepenthes) wrote on 2019-11-07: Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic on Dell XPS 13 9370

#20

Same issue here, Dell 9570. It seems to happen more often when I have Bluetooth devices associated.

[ 5954.587078] ath10k_pci 0000:3b:00.0: firmware crashed! (guid 29b90296-0ef9-4140-8a80-abe8ab57a186)
[ 5954.587092] ath10k_pci 0000:3b:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[ 5954.587096] ath10k_pci 0000:3b:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 5954.588808] ath10k_pci 0000:3b:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1
[ 5954.590111] ath10k_pci 0000:3b:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
[ 5954.590117] ath10k_pci 0000:3b:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 5954.600293] ath10k_pci 0000:3b:00.0: failed to get memcpy hi address for firmware address 4: -16
[ 5954.600296] ath10k_pci 0000:3b:00.0: failed to read firmware dump area: -16
[ 5954.600300] ath10k_pci 0000:3b:00.0: Copy Engine register dump:
[ 5954.600336] ath10k_pci 0000:3b:00.0: [00]: 0x00034400 14 14 3 3
[ 5954.600369] ath10k_pci 0000:3b:00.0: [01]: 0x00034800 6 6 83 84
[ 5954.600465] ath10k_pci 0000:3b:00.0: [02]: 0x00034c00 57 57 55 56
[ 5954.600502] ath10k_pci 0000:3b:00.0: [03]: 0x00035000 9 9 11 9
[ 5954.600547] ath10k_pci 0000:3b:00.0: [04]: 0x00035400 3521 3517 31 223
[ 5954.600592] ath10k_pci 0000:3b:00.0: [05]: 0x00035800 0 0 64 0
[ 5954.600621] ath10k_pci 0000:3b:00.0: [06]: 0x00035c00 30 29 0 30
[ 5954.600636] ath10k_pci 0000:3b:00.0: [07]: 0x00036000 1 1 1 0
[ 5954.620584] ath10k_pci 0000:3b:00.0: failed to read hi_board_data address: -28
[ 5954.706228] ieee80211 phy0: Hardware restart was requested
[ 5954.921384] ath10k_pci 0000:3b:00.0: UART prints enabled
[ 5954.990174] ath10k_pci 0000:3b:00.0: unsupported HTC service id: 1536
[ 5955.493975] ath10k_pci 0000:3b:00.0: device successfully recovered
[ 6004.131362] wlp59s0: deauthenticating from b4:fb:e4:4b:1e:49 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 6007.923710] ath10k_pci 0000:3b:00.0: UART prints enabled
[ 6007.992931] ath10k_pci 0000:3b:00.0: unsupported HTC service id: 1536

Same issue here, Dell 9570. It seems to happen more often when I have Bluetooth devices associated.

[ 5954.587078] ath10k_pci 0000:3b:00.0: firmware crashed! (guid 29b90296-0ef9-4140-8a80-abe8ab57a186)
[ 5954.587092] ath10k_pci 0000:3b:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[ 5954.587096] ath10k_pci 0000:3b:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 5954.588808] ath10k_pci 0000:3b:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1
[ 5954.590111] ath10k_pci 0000:3b:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
[ 5954.590117] ath10k_pci 0000:3b:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 5954.600293] ath10k_pci 0000:3b:00.0: failed to get memcpy hi address for firmware address 4: -16
[ 5954.600296] ath10k_pci 0000:3b:00.0: failed to read firmware dump area: -16
[ 5954.600300] ath10k_pci 0000:3b:00.0: Copy Engine register dump:
[ 5954.600336] ath10k_pci 0000:3b:00.0: [00]: 0x00034400  14  14   3   3
[ 5954.600369] ath10k_pci 0000:3b:00.0: [01]: 0x00034800   6   6  83  84
[ 5954.600465] ath10k_pci 0000:3b:00.0: [02]: 0x00034c00  57  57  55  56
[ 5954.600502] ath10k_pci 0000:3b:00.0: [03]: 0x00035000   9   9  11   9
[ 5954.600547] ath10k_pci 0000:3b:00.0: [04]: 0x00035400 3521 3517  31 223
[ 5954.600592] ath10k_pci 0000:3b:00.0: [05]: 0x00035800   0   0  64   0
[ 5954.600621] ath10k_pci 0000:3b:00.0: [06]: 0x00035c00  30  29   0  30
[ 5954.600636] ath10k_pci 0000:3b:00.0: [07]: 0x00036000   1   1   1   0
[ 5954.620584] ath10k_pci 0000:3b:00.0: failed to read hi_board_data address: -28
[ 5954.706228] ieee80211 phy0: Hardware restart was requested
[ 5954.921384] ath10k_pci 0000:3b:00.0: UART prints enabled
[ 5954.990174] ath10k_pci 0000:3b:00.0: unsupported HTC service id: 1536
[ 5955.493975] ath10k_pci 0000:3b:00.0: device successfully recovered
[ 6004.131362] wlp59s0: deauthenticating from b4:fb:e4:4b:1e:49 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 6007.923710] ath10k_pci 0000:3b:00.0: UART prints enabled
[ 6007.992931] ath10k_pci 0000:3b:00.0: unsupported HTC service id: 1536

Revision history for this message

Olivier P (olivierp) wrote on 2020-04-21:

#21

Same issue here.

Tried latest firmware (WLAN.RM.4.4.1-00151-QCARMSWPZ-2) but no improvement .

You-Sheng Yang (vicamo) on 2020-04-22

tags:

added: hwe-networking-wifi

Revision history for this message

Michaël Van Damme (mvdamme) wrote on 2020-05-28:

#22

Same problem for me. Dell XPS 13 9380 ubuntu edition.
Happens at least once a day, sometimes more often. Seems to happen more when the network load is not high.
I've upgraded to the latest firmware, but without improvement.

Revision history for this message

Olivier P (olivierp) wrote on 2020-05-29:

#23

On my XPS 9370 the problem was only reproductible on 1 type of wireless access point and only when the network SSID was set to use both the 2.4Ghz and 5Ghz bands.

Configuring the access point to have different SSID for the 2.4Ghz and 5Ghz WIFI bands solved the issue.

You-Sheng Yang (vicamo) on 2020-05-29

summary:

- Wireless regularly breaking (ath10k firmware crashed!) after upgrade to
- Cosmic on Dell XPS 13 9370
+ Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless
+ regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic on
+ Dell XPS 13 9370

Revision history for this message

Mike Meehan (mjmeehan) wrote on 2020-07-01:

#24

This broke again for me on upgrade from Bionic to Cosmic on the Dell XPS 9380. When it starts to go bad it requires a reload of the driver every 10 minutes or so. The dmesg log says "device successfully recovered, but it fails to rejoin any wifi networks and doesn't work properly until I rmmod ath10k_pci; modprobe ath10k_pci. dmesg logs follow, I'm on the latest 4.4.1 firmware (not sure if I need c1/c2/c3)

[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: firmware crashed! (guid 13b1b96d-1e2b-4abf-b1dc-8284c92d3247)
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00151-QCARMSWPZ-2 api 6 features wowlan,ignore-otp,mfp crc32 64160d13
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 e74847dc
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: failed to get memcpy hi address for firmware address 4: -16
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -16
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: [00]: 0x00034400 11 11 3 3
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: [01]: 0x00034800 25 25 358 359
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: [02]: 0x00034c00 42 42 40 41
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: [03]: 0x00035000 1 1 3 1
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: [04]: 0x00035400 4319 4309 171 107
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: [05]: 0x00035800 0 0 64 0
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: [06]: 0x00035c00 25 25 22 22
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: [07]: 0x00036000 1 1 1 0
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: failed to read hi_board_data address: -28
[Wed Jul 1 12:51:26 2020] ieee80211 phy21: Hardware restart was requested
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536
[Wed Jul 1 12:51:26 2020] ath10k_pci 0000:02:00.0: device successfully recovered
[Wed Jul 1 12:52:36 2020] ath10k_pci 0000:02:00.0: firmware crashed! (guid 74d29bb1-19c4-447c-bdd5-40c6eda525fd)

Would crash dumps help?

[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: firmware crashed! (guid 13b1b96d-1e2b-4abf-b1dc-8284c92d3247)
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00151-QCARMSWPZ-2 api 6 features wowlan,ignore-otp,mfp crc32 64160d13
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 e74847dc
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: failed to get memcpy hi address for firmware address 4: -16
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -16
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: [00]: 0x00034400  11  11   3   3
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: [01]: 0x00034800  25  25 358 359
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: [02]: 0x00034c00  42  42  40  41
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: [03]: 0x00035000   1   1   3   1
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: [04]: 0x00035400 4319 4309 171 107
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: [05]: 0x00035800   0   0  64   0
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: [06]: 0x00035c00  25  25  22  22
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: [07]: 0x00036000   1   1   1   0
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: failed to read hi_board_data address: -28
[Wed Jul  1 12:51:26 2020] ieee80211 phy21: Hardware restart was requested
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536
[Wed Jul  1 12:51:26 2020] ath10k_pci 0000:02:00.0: device successfully recovered
[Wed Jul  1 12:52:36 2020] ath10k_pci 0000:02:00.0: firmware crashed! (guid 74d29bb1-19c4-447c-bdd5-40c6eda525fd)

Would crash dumps help?

Revision history for this message

Mike Meehan (mjmeehan) wrote on 2020-07-01:

#25

oliverp, my wifi access point uses different SSIDs for 2.4 and 5 G and still has this problem.

Revision history for this message

Mike Meehan (mjmeehan) wrote on 2020-07-01:

#26

Sorry, correction above, this broke on the upgrade to Ubuntu 20.04 Focal.

tags:

added: focal

Revision history for this message

Robbob (rob-kirkbride) wrote on 2020-07-04:

#27

Same for me, crashing on XPS 13 9370 with Ubuntu 20.04 Focal and 5.4.0-40-generic #44-Ubuntu SMP

Revision history for this message

Weiguang Cui (weiguang) wrote on 2020-07-29:

#28

Hi
I have the same problem with XPS 13 9380, Ubuntu 20.04.1 LTS, 5.4.0-42-generic

Revision history for this message

Weiguang Cui (weiguang) wrote on 2020-07-29:

#29

And sometimes it can be recovered, but not always...
[28023.806953] ath10k_pci 0000:02:00.0: firmware crashed! (guid e4f47d81-ff1a-4173-9847-bbc2770ee439)
[28023.806968] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[28023.806973] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[28023.808665] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1
[28023.810003] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b
[28023.810009] ath10k_pci 0000:02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[28023.820139] ath10k_pci 0000:02:00.0: failed to get memcpy hi address for firmware address 4: -16
[28023.820140] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -16
[28023.820142] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[28023.820151] ath10k_pci 0000:02:00.0: [00]: 0x00034400 11 11 3 3
[28023.820158] ath10k_pci 0000:02:00.0: [01]: 0x00034800 23 23 356 357
[28023.820166] ath10k_pci 0000:02:00.0: [02]: 0x00034c00 60 59 58 59
[28023.820173] ath10k_pci 0000:02:00.0: [03]: 0x00035000 14 14 16 14
[28023.820181] ath10k_pci 0000:02:00.0: [04]: 0x00035400 4335 4331 182 118
[28023.820188] ath10k_pci 0000:02:00.0: [05]: 0x00035800 0 0 64 0
[28023.820196] ath10k_pci 0000:02:00.0: [06]: 0x00035c00 8 8 4 4
[28023.820203] ath10k_pci 0000:02:00.0: [07]: 0x00036000 1 1 1 0
[28023.844105] ath10k_pci 0000:02:00.0: failed to read hi_board_data address: -28
[28023.926083] ieee80211 phy0: Hardware restart was requested
[28024.133190] ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536
[28024.236270] ath10k_pci 0000:02:00.0: device successfully recovered
[28117.136734] wlp2s0: deauthenticating from 18:35:d1:ba:ad:67 by local choice (Reason: 3=DEAUTH_LEAVING)
[28119.676844] ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536

Revision history for this message

Julian Edwards (julian-edwards) wrote on 2020-10-03:

#30

Bionic was rock solid for me - Focal has been a nightmare of crashes. I can disconnect from the AP and reconnect and it comes back to life.

Revision history for this message

David Kowis (dkowis) wrote on 2020-11-10:

#31

This happens for me quite often on 20.10:

02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)

I can barely stay attached to wifi.

Revision history for this message

Mike Meehan (mjmeehan) wrote on 2020-11-10:

#32

Broke again on upgrade from Focal to Groovy.

Revision history for this message

mohsen (mohsenzr) wrote on 2020-12-02:

#33

has anyone solve the issue? it's driving me mad!

Revision history for this message

Igor Bubelov (bubelov) wrote on 2020-12-05:

#34

Just installed 20.10 and WiFi crashed in a few hours.

sudo dmesg --follow --human

[Dec 5 14:37] device-mapper: table: 253:2: linear: Device lookup failed
[ +0.000003] device-mapper: ioctl: error adding target to table
[Dec 5 14:38] ath10k_pci 0000:02:00.0: firmware crashed! (guid a21dbcfc-380d-40b9-8d18-2ab61792e770)
[ +0.000020] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[ +0.000006] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ +0.002174] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1
[ +0.001569] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b
[ +0.000007] ath10k_pci 0000:02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ +0.000149] ath10k_pci 0000:02:00.0: firmware register dump:
[ +0.000009] ath10k_pci 0000:02:00.0: [00]: 0x05030000 0x000015B3 0x009E2680 0x00955B31
[ +0.000006] ath10k_pci 0000:02:00.0: [04]: 0x009E2680 0x00060330 0x00000005 0x000000FF
[ +0.000005] ath10k_pci 0000:02:00.0: [08]: 0x0040A054 0x00000000 0x00000010 0x00429BE0
[ +0.000005] ath10k_pci 0000:02:00.0: [12]: 0x00000009 0x00000000 0x00952F6C 0x00952F77
[ +0.000005] ath10k_pci 0000:02:00.0: [16]: 0x00952CC4 0x00910712 0x00000000 0x0091080D
[ +0.000005] ath10k_pci 0000:02:00.0: [20]: 0x409E2680 0x0040E928 0x00000001 0x0049C444
[ +0.000005] ath10k_pci 0000:02:00.0: [24]: 0x809DDCEE 0x0040E988 0x0040E998 0xC09E2680
[ +0.000005] ath10k_pci 0000:02:00.0: [28]: 0x809E6F21 0x0040E9B8 0x0040A054 0x00000001
[ +0.000005] ath10k_pci 0000:02:00.0: [32]: 0x809F5C2D 0x0040E9E8 0x000003E8 0x00499EA8
[ +0.000005] ath10k_pci 0000:02:00.0: [36]: 0x809143A7 0x0040EA68 0x00499EB4 0x00429FC0
[ +0.000004] ath10k_pci 0000:02:00.0: [40]: 0x809F3A57 0x0040EA88 0x00411770 0x004117E0
[ +0.000005] ath10k_pci 0000:02:00.0: [44]: 0x809F37B2 0x0040EAA8 0x00000000 0x00000000
[ +0.000006] ath10k_pci 0000:02:00.0: [48]: 0x80911210 0x0040EAC8 0x00000008 0x00404130
[ +0.000009] ath10k_pci 0000:02:00.0: [52]: 0x80911154 0x0040EB28 0x00400000 0x00000000
[ +0.000005] ath10k_pci 0000:02:00.0: [56]: 0x8091122D 0x0040EB48 0x00000000 0x00400600
[ +0.000005] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[ +0.000015] ath10k_pci 0000:02:00.0: [00]: 0x00034400 11 11 3 3
[ +0.000013] ath10k_pci 0000:02:00.0: [01]: 0x00034800 22 22 67 68
[ +0.000013] ath10k_pci 0000:02:00.0: [02]: 0x00034c00 27 27 26 27
[ +0.000013] ath10k_pci 0000:02:00.0: [03]: 0x00035000 13 13 15 13
[ +0.000013] ath10k_pci 0000:02:00.0: [04]: 0x00035400 805 805 205 148
[ +0.000013] ath10k_pci 0000:02:00.0: [05]: 0x00035800 0 0 64 0
[ +0.000013] ath10k_pci 0000:02:00.0: [06]: 0x00035c00 1 1 12 12
[ +0.000013] ath10k_pci 0000:02:00.0: [07]: 0x00036000 0 0 0 0
[ +0.095814] ieee80211 phy0: Hardware restart was requested
[ +0.310986] ath10k_pci 0000:02:00.0: device successfully recovered

Despite the last message, WiFi didn't recover. I had to toggle it in Settings in order to get back online.

Just installed 20.10 and WiFi crashed in a few hours.

sudo dmesg --follow --human

[Dec 5 14:37] device-mapper: table: 253:2: linear: Device lookup failed
[  +0.000003] device-mapper: ioctl: error adding target to table
[Dec 5 14:38] ath10k_pci 0000:02:00.0: firmware crashed! (guid a21dbcfc-380d-40b9-8d18-2ab61792e770)
[  +0.000020] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[  +0.000006] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[  +0.002174] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1
[  +0.001569] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b
[  +0.000007] ath10k_pci 0000:02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[  +0.000149] ath10k_pci 0000:02:00.0: firmware register dump:
[  +0.000009] ath10k_pci 0000:02:00.0: [00]: 0x05030000 0x000015B3 0x009E2680 0x00955B31
[  +0.000006] ath10k_pci 0000:02:00.0: [04]: 0x009E2680 0x00060330 0x00000005 0x000000FF
[  +0.000005] ath10k_pci 0000:02:00.0: [08]: 0x0040A054 0x00000000 0x00000010 0x00429BE0
[  +0.000005] ath10k_pci 0000:02:00.0: [12]: 0x00000009 0x00000000 0x00952F6C 0x00952F77
[  +0.000005] ath10k_pci 0000:02:00.0: [16]: 0x00952CC4 0x00910712 0x00000000 0x0091080D
[  +0.000005] ath10k_pci 0000:02:00.0: [20]: 0x409E2680 0x0040E928 0x00000001 0x0049C444
[  +0.000005] ath10k_pci 0000:02:00.0: [24]: 0x809DDCEE 0x0040E988 0x0040E998 0xC09E2680
[  +0.000005] ath10k_pci 0000:02:00.0: [28]: 0x809E6F21 0x0040E9B8 0x0040A054 0x00000001
[  +0.000005] ath10k_pci 0000:02:00.0: [32]: 0x809F5C2D 0x0040E9E8 0x000003E8 0x00499EA8
[  +0.000005] ath10k_pci 0000:02:00.0: [36]: 0x809143A7 0x0040EA68 0x00499EB4 0x00429FC0
[  +0.000004] ath10k_pci 0000:02:00.0: [40]: 0x809F3A57 0x0040EA88 0x00411770 0x004117E0
[  +0.000005] ath10k_pci 0000:02:00.0: [44]: 0x809F37B2 0x0040EAA8 0x00000000 0x00000000
[  +0.000006] ath10k_pci 0000:02:00.0: [48]: 0x80911210 0x0040EAC8 0x00000008 0x00404130
[  +0.000009] ath10k_pci 0000:02:00.0: [52]: 0x80911154 0x0040EB28 0x00400000 0x00000000
[  +0.000005] ath10k_pci 0000:02:00.0: [56]: 0x8091122D 0x0040EB48 0x00000000 0x00400600
[  +0.000005] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[  +0.000015] ath10k_pci 0000:02:00.0: [00]: 0x00034400  11  11   3   3
[  +0.000013] ath10k_pci 0000:02:00.0: [01]: 0x00034800  22  22  67  68
[  +0.000013] ath10k_pci 0000:02:00.0: [02]: 0x00034c00  27  27  26  27
[  +0.000013] ath10k_pci 0000:02:00.0: [03]: 0x00035000  13  13  15  13
[  +0.000013] ath10k_pci 0000:02:00.0: [04]: 0x00035400 805 805 205 148
[  +0.000013] ath10k_pci 0000:02:00.0: [05]: 0x00035800   0   0  64   0
[  +0.000013] ath10k_pci 0000:02:00.0: [06]: 0x00035c00   1   1  12  12
[  +0.000013] ath10k_pci 0000:02:00.0: [07]: 0x00036000   0   0   0   0
[  +0.095814] ieee80211 phy0: Hardware restart was requested
[  +0.310986] ath10k_pci 0000:02:00.0: device successfully recovered

Despite the last message, WiFi didn't recover. I had to toggle it in Settings in order to get back online.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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

Ubuntulinux package

Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic on Dell XPS 13 9370

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package