Page MenuHomeVyOS Platform
Create Task
Maniphest T5331

ath10k_pci not functioning
Closed, ResolvedPublicBUG
Actions

Description

My WiFi is not being detected in 1.3.3, or in 1.3.2.

Relevant dmesg output:

[ 19.013393] ath10k_pci 0000:03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 20.181578] random: dbus-daemon: uninitialized urandom read (12 bytes read)
[ 20.497930] random: crng init done
[ 20.983288] Process accounting resumed
[ 22.068925] ath10k_pci 0000:03:00.0: failed to read device register, device is gone
[ 22.076952] ath10k_pci 0000:03:00.0: failed to wait for target after cold reset: -5
[ 22.076954] ath10k_pci 0000:03:00.0: failed to reset chip: -5
[ 22.085242] ath10k_pci: probe of 0000:03:00.0 failed with error -5

lsmod output:

lsmod | grep ath10k
ath10k_pci 45056 0
ath10k_core 397312 1 ath10k_pci
ath 40960 1 ath10k_core
mac80211 565248 1 ath10k_core
cfg80211 405504 3 ath,mac80211,ath10k_core

lspci output

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

Subsystem: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
Flags: fast devsel, IRQ 16
Memory at d1000000 (64-bit, non-prefetchable) [disabled] [size=2M]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/8 Maskable+ 64bit-
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Virtual Channel
Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [178] Latency Tolerance Reporting
Capabilities: [180] L1 PM Substates
Kernel modules: ath10k_pci

Details

Difficulty level
Unknown (require assessment)
Version
1.3.3
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Unspecified (please specify)

Event Timeline

giga1699 created this task.Jul 1 2023, 7:50 PM
giga1699 added a comment.Jul 1 2023, 8:34 PM

Attempted a modprobe -r ath10k_pci and the re-load the module. The following dmesg is what I saw after.

[ 89.280354] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 89.280821] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 89.280899] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 89.280902] cfg80211: failed to load regulatory.db
[ 89.306238] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
[ 89.384616] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x00000000 at 0x00034400: -110
[ 89.462539] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x00000000 at 0x00034404: -110
[ 89.540379] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00034410: -110
[ 89.618324] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xffff0000 at 0x00034410: -110
[ 89.696225] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003444c: -110
[ 89.774139] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xffff0000 at 0x0003444c: -110
[ 89.852049] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x00000000 at 0x00034408: -110
[ 89.929953] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x00000000 at 0x0003440c: -110
[ 90.007882] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00034450: -110
[ 90.085779] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xffff0000 at 0x00034450: -110
[ 94.448246] ath10k_warn: 55 callbacks suppressed
[ 94.448249] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xffff0000 at 0x00035c4c: -110
[ 94.526177] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x00000000 at 0x00035c08: -110
[ 94.603838] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x00000000 at 0x00035c0c: -110
[ 94.681406] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00035c50: -110
[ 94.759063] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xffff0000 at 0x00035c50: -110
[ 94.836700] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x00000000 at 0x00036000: -110
[ 94.914664] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0x00000000 at 0x00036004: -110
[ 94.992588] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036010: -110
[ 95.070459] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xffff0000 at 0x00036010: -110
[ 95.148412] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003604c: -110
[ 99.197909] ath10k_pci 0000:03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 99.604462] ath10k_warn: 54 callbacks suppressed
[ 99.604485] ath10k_pci 0000:03:00.0: failed to wake target for write32 of 0xfffffffe at 0x00080008: -110
[ 99.704179] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110
[ 99.782123] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110
[ 99.860039] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110
[ 99.937980] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110
[ 100.015915] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110
[ 100.093816] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110
[ 100.171742] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110
[ 100.249688] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110
[ 100.327537] ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x0003a028: -110
[ 103.054220] ath10k_pci 0000:03:00.0: failed to read device register, device is gone
[ 103.062256] ath10k_pci 0000:03:00.0: failed to reset chip: -5
[ 103.069162] ath10k_pci: probe of 0000:03:00.0 failed with error -5

pasik added a subscriber: pasik.Jul 1 2023, 8:56 PM
giga1699 added a comment.Jul 1 2023, 8:57 PM

Tried the following:

echo 1 > /sys/bus/pci/devices/0000:03:00.0/remove
echo 1 > /sys/bus/pci/rescan

dmesg follows:

[ 1219.817740] pci 0000:03:00.0: [168c:003e] type 00 class 0x028000
[ 1219.817834] pci 0000:03:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
[ 1219.818201] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
[ 1219.818635] pcieport 0000:00:1c.3: ASPM: current common clock configuration is broken, reconfiguring
[ 1219.821287] pci 0000:03:00.0: BAR 0: assigned [mem 0xd1000000-0xd11fffff 64bit]
[ 1219.829842] ath10k_pci 0000:03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 1220.098494] ath10k_pci 0000:03:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 168c:3361
[ 1220.098499] ath10k_pci 0000:03:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 1 testmode 0
[ 1220.099280] ath10k_pci 0000:03:00.0: firmware ver WLAN.RM.4.4.1-00157-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 90eebefb
[ 1220.175409] ath10k_pci 0000:03:00.0: board_file api 2 bmi_id N/A crc32 318825bf
[ 1220.248833] ath10k_warn: 36 callbacks suppressed
[ 1220.248912] ath10k_pci 0000:03:00.0: unsupported HTC service id: 1536
[ 1220.268604] ath10k_pci 0000:03:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 1220.328629] ath: EEPROM regdomain: 0x6c
[ 1220.328633] ath: EEPROM indicates we should expect a direct regpair map
[ 1220.328635] ath: Country alpha2 being used: 00
[ 1220.328636] ath: Regpair used: 0x6c

wlan0 now shows.

However, after a reboot it is still not showing.

giga1699 added a comment.Jul 1 2023, 9:14 PM

VyOS 1.4-rolling-202306280317 show the following additional dmesg items

[ 23.510821] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 23.547839] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 23.559026] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
[ 24.021656] ath10k_pci 0000:03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 27.088255] ath10k_pci 0000:03:00.0: failed to read device register, device is gone
[ 27.096000] ath10k_pci 0000:03:00.0: failed to wait for target after cold reset: -5
[ 27.096005] ath10k_pci 0000:03:00.0: failed to reset chip: -5
[ 27.107045] ath10k_pci: probe of 0000:03:00.0 failed with error -5
[ 27.107080] ------------[ cut here ]------------
[ 27.107084] WARNING: CPU: 1 PID: 618 at kernel/irq/msi.c:182 msi_device_data_release+0x25/0x30
[ 27.107102] Modules linked in: ath10k_pci(+) ath10k_core ath mac80211 cfg80211 intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul rfkill ghash_clmulni_intel libarc4 sha512_ssse3 sha512_generic aesni_intel crypto_simd cryptd intel_cstate at24 pcspkr evdev iTCO_wdt iTCO_vendor_support processor_thermal_deviced
[ 27.107280] CPU: 1 PID: 618 Comm: (udev-worker) Not tainted 6.1.35-amd64-vyos #1
[ 27.107287] Hardware name: Protectli FW2B/FW2B, BIOS v4.9.0.3 10/14/2022
[ 27.107291] RIP: 0010:msi_device_data_release+0x25/0x30
[ 27.107301] Code: 80 00 00 00 00 48 83 7e 38 00 53 48 89 fb 75 1a 48 8d 7e 30 e8 3c 35 7d 00 48 c7 83 28 02 00 00 00 00 00 00 5b c3 cc cc cc cc <0f> 0b eb e2 0f 1f 80 00 00 00 00 48 8b bf 28 02 00 00 48 83 c7 10
[ 27.107306] RSP: 0000:ffffa97ac0647c38 EFLAGS: 00010286
[ 27.107313] RAX: ffffffffafeef380 RBX: ffff9a99c0a900d0 RCX: ffff9a99cbdb4800
[ 27.107317] RDX: 0000000000000001 RSI: ffff9a99cbdb4828 RDI: ffff9a99c0a900d0
[ 27.107321] RBP: ffff9a99c61af880 R08: ffffffffb0e4ee68 R09: 0000000000000048
[ 27.107326] R10: 0000000000000037 R11: ffff9a99ce45d240 R12: ffffa97ac0647c70
[ 27.107329] R13: ffff9a99c0a900d0 R14: ffff9a99c0a90364 R15: 0000000000000000
[ 27.107334] FS: 00007f5bda6178c0(0000) GS:ffff9a9a3bd00000(0000) knlGS:0000000000000000
[ 27.107339] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 27.107344] CR2: 00007f3bc7a4f000 CR3: 0000000107cca000 CR4: 00000000001006e0
[ 27.107349] Call Trace:
[ 27.107353] <TASK>
[ 27.107359] ? warn+0x78/0xc0
[ 27.107367] ? msi_device_data_release+0x25/0x30
[ 27.107375] ? report_bug+0xe6/0x170
[ 27.107384] ? handle_bug+0x41/0x70
[ 27.107393] ? exc_invalid_op+0x13/0x60
[ 27.107400] ? asm_exc_invalid_op+0x16/0x20
[ 27.107409] ? get_cached_msi_msg+0x30/0x30
[ 27.107418] ? msi_device_data_release+0x25/0x30
[ 27.107425] release_nodes+0x3b/0xb0
[ 27.107433] devres_release_all+0x83/0xc0
[ 27.107442] device_unbind_cleanup+0x9/0x70
[ 27.107450] really_probe+0x23d/0x380
[ 27.107456] ? pm_runtime_barrier+0x4b/0x80
[ 27.107463] driver_probe_device+0x73/0x120
[ 27.107470] driver_probe_device+0x1a/0x90
[ 27.107477] driver_attach+0xc9/0x1c0
[ 27.107484] ? device_attach_driver+0x110/0x110
[ 27.107490] bus_for_each_dev+0x71/0xb0
[ 27.107497] bus_add_driver+0x1a9/0x200
[ 27.107504] driver_register+0x84/0xe0
[ 27.107511] ? 0xffffffffc0da9000
[ 27.107517] ath10k_pci_init+0x1a/0x1000 [ath10k_pci]
[ 27.107536] do_one_initcall+0x41/0x200
[ 27.107545] ? kmalloc_trace+0x21/0x90
[ 27.107553] do_init_module+0x45/0x1c0
[ 27.107562] __do_sys_finit_module+0xac/0x120
[ 27.107571] do_syscall_64+0x3a/0x90
[ 27.107579] entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 27.107586] RIP: 0033:0x7f5bdad234f9
[ 27.107592] Code: 08 89 e8 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d7 08 0d 00 f7 d8 64 89 01 48
[ 27.107597] RSP: 002b:00007ffedde79268 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[ 27.107604] RAX: ffffffffffffffda RBX: 00005640361b9870 RCX: 00007f5bdad234f9
[ 27.107608] RDX: 0000000000000000 RSI: 00007f5bdaeb6efd RDI: 0000000000000013
[ 27.107612] RBP: 00007f5bdaeb6efd R08: 0000000000000000 R09: 00005640361bad50
[ 27.107616] R10: 0000000000000013 R11: 0000000000000246 R12: 0000000000020000
[ 27.107620] R13: 0000000000000000 R14: 00005640362751b0 R15: 0000564034fe8e4f
[ 27.107626] </TASK>
[ 27.107629] ---[ end trace 0000000000000000 ]---

giga1699 renamed this task from atk10k_pci not functioning to ath10k_pci not functioning.Jul 2 2023, 2:23 AM
giga1699 added a comment.Jul 5 2023, 5:41 PM

In talking with the vendor, this appears to be an incompatibility with the WiFi card and the coreboot BIOS installed on the device. Tested with a second device that had a different card installed, and no such errors are present now.

giga1699 closed this task as Resolved.Jul 5 2023, 5:42 PM
giga1699 claimed this task.