FS#55630 - [linux] ATH10k firmware crash in 4.13.1-2

Attached to Project: Arch Linux
Opened by Mal Haak (insanemal) - Thursday, 14 September 2017, 03:32 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 18 September 2017, 00:58 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
linux 4.13.1-2 breaks ATH10K wifi.

Firmware crashes on load.

Downgrade to 4.13.1-1 everything works fine.


Additional info:
* package version(s)
* config and/or log files etc.

Sep 14 13:02:49 mals_xps kernel: ath10k_pci 0000:3a:00.0: enabling device (0000 -> 0002)
Sep 14 13:02:49 mals_xps kernel: ath10k_pci 0000:3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Sep 14 13:02:50 mals_xps kernel: ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
Sep 14 13:02:50 mals_xps kernel: ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
Sep 14 13:02:50 mals_xps kernel: ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6 features wowlan,ignore-otp crc32 4d458559
Sep 14 13:02:50 mals_xps kernel: ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 07ee144e
Sep 14 13:02:50 mals_xps NetworkManager[300]: <info> [1505358170.9993] rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.4/0000:3a:00.0/ieee80211/phy0/rfkill1) (driver ath10k_pci)
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0 wlp58s0: renamed from wlan0
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: firmware crashed! (uuid ce023716-13b3-4281-a7b1-771e24dd82e9)
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6 features wowlan,ignore-otp crc32 4d458559
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 07ee144e
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to get memcpy hi address for firmware address 4: -16
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to read firmware dump area: -16
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: Copy Engine register dump:
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295
Sep 14 13:02:51 mals_xps kernel: ath10k_pci 0000:3a:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295
Sep 14 13:02:52 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to receive control response completion, polling..
Sep 14 13:02:52 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0x00000001 at 0x00034430: -110
Sep 14 13:02:52 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x00034444: -110
Sep 14 13:02:52 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0x0000001e at 0x00034430: -110
Sep 14 13:02:52 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0x00000001 at 0x00034830: -110
Sep 14 13:02:52 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0x00000001 at 0x00035430: -110
Sep 14 13:02:52 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x00035444: -110
Sep 14 13:02:52 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0x0000001e at 0x00035430: -110
Sep 14 13:02:54 mals_xps kernel: ath10k_pci 0000:3a:00.0: ctl_resp never came in (-110)
Sep 14 13:02:54 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to connect to HTC: -110
Sep 14 13:02:55 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x00035c2c: -110
Sep 14 13:02:55 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0xffffffe1 at 0x00035c2c: -110
Sep 14 13:02:55 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003602c: -110
Sep 14 13:02:55 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0xfffffffe at 0x0003602c: -110
Sep 14 13:02:56 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x00036034: -110
Sep 14 13:02:56 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0xfffff81f at 0x00036034: -110
Sep 14 13:02:56 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003602c: -110
Sep 14 13:02:56 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0xffffffe1 at 0x0003602c: -110
Sep 14 13:02:56 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0x00000000 at 0x0003a008: -110
Sep 14 13:02:56 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for write32 of 0x0007fc00 at 0x0003a014: -110
Sep 14 13:03:00 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:00 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:00 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:00 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:00 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:01 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:01 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:01 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:01 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:01 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:02 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to read device register, device is gone
Sep 14 13:03:05 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:05 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:05 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:05 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:06 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:06 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:06 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:06 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:06 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:06 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:08 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to read device register, device is gone
Sep 14 13:03:10 mals_xps kernel: ath10k_pci 0000:3a:00.0: Could not init core: -110
Sep 14 13:03:10 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:10 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:11 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:11 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:11 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:11 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:11 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:11 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:11 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:11 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to wake target for read32 at 0x0003a028: -110
Sep 14 13:03:13 mals_xps kernel: ath10k_pci 0000:3a:00.0: failed to read device register, device is gone



Steps to reproduce: Upgrade to 4.13.1-2
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Monday, 18 September 2017, 00:58 GMT
Reason for closing:  Fixed
Additional comments about closing:  per OP request: now works in linux 4.13.2-1
Comment by loqs (loqs) - Thursday, 14 September 2017, 17:50 GMT
4.13.1-2 contained only one patch that was for a bluetooth remote root exploit . It seems somewhat strange it would cause a crash on firmware load.
https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/linux&id=994212d3db4186aba0d3ae1b9a27146bbe0e64d3
If it still occurs using 4.13.2-1 I would recommend you report it upstream as per
https://wiki.archlinux.org/index.php/Reporting_bug_guidelines#Upstream_or_Arch.3F
Comment by Eli Schwartz (eschwartz) - Friday, 15 September 2017, 16:27 GMT
  • Field changed: Status (Unconfirmed → Waiting on Response)
  • Field changed: Severity (High → Medium)
Please confirm whether this can be reproduced on the latest linux 4.13.2-1 package in testing.
Comment by Mal Haak (insanemal) - Monday, 18 September 2017, 00:44 GMT
Ath10k and bluetooth share module in XPS13.

4.13.2-1 fixes it.

Please close

Loading...