Network interface taking a long time to come up

[Kalle Valo]

Jens Christian Hillerup <jc at veo.co> writes:

> Hello
>
> I'm trying to get a QCA6174-based PCIe card online on the NVIDIA Tegra
> platform. Running kernel 4.9.253-l4t-r32.6. The card is detected and
> visible in lspci (+ lsusb for the Bluetooth parts), but after loading
> the ath10k_pci driver it takes about 2 minutes for the network
> interface to actually appear.
>
> In fact, it takes so close to 120 seconds that I believe it could be
> due to some kind of timeout.
>
>     $ ls -1 /lib/firmware/ath10k/QCA6174/hw3.0/
>     board-2.bin
>     board.bin
>     firmware-4.bin
>     firmware-5.bin
>     firmware-6.bin
>     firmware-sdio-6.bin
>
>     $ dmesg
>     <snip>
>     [    9.932518] ath10k_pci 0004:01:00.0: enabling device (0000 -> 0002)
>     [    9.933364] ath10k_pci 0004:01:00.0: pci irq msi oper_irq_mode
> 2 irq_mode 0 reset_mode 0
>     [   10.211615] ath10k_pci 0004:01:00.0: Direct firmware load for
> ath10k/pre-cal-pci-0004:01:00.0.bin failed with error -2
>     [   10.211835] ath10k_pci 0004:01:00.0: Falling back to user helper
>     <snip>
>     [   71.009583] ath10k_pci 0004:01:00.0: Direct firmware load for
> ath10k/cal-pci-0004:01:00.0.bin failed with error -2
>     [   71.009612] ath10k_pci 0004:01:00.0: Falling back to user helper
>     [  132.469576] ath10k_pci 0004:01:00.0: qca6174 hw3.2 target
> 0x05030000 chip_id 0x00340aff sub 11ad:0513
>     [  132.469588] ath10k_pci 0004:01:00.0: kconfig debug 0 debugfs 1
> tracing 0 dfs 0 testmode 0
>     [  132.470831] ath10k_pci 0004:01:00.0: firmware ver
> WLAN.RM.4.4.1-00157-QCARMSWPZ-1 api 5 features wowlan,ignore-otp,mfp
> crc32 90eebefb
>     [  132.550108] ath10k_pci 0004:01:00.0: board_file api 2 bmi_id
> N/A crc32 318825bf

The 60 second timeout in firmware loading points out to the user space
firmware loader helper failing. This has come few times in the past and
is not related to ath10k, but I have forgetten the details already. Try
disabling CONFIG_FW_LOADER_USER_HELPER_FALLBACK and tinkering with other
firmware loader settings. Also google should be able to help you, this
was pretty frequent problem in the past. Ah, you are using 4.9 kernel
which is already five years old.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches