ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* ath10k_sdio: Long time for loading firmware and RCU errors
@ 2021-05-26  0:40 Fabio Estevam
  2021-06-02 22:51 ` Fabio Estevam
  0 siblings, 1 reply; 2+ messages in thread
From: Fabio Estevam @ 2021-05-26  0:40 UTC (permalink / raw)
  To: Christian Hewitt, Gary Bisson, gerg, erik.stromdahl, Kalle Valo
  Cc: linux-wireless, ath10k

Hi,

I am using the QCA9377 chip on an imx6dl-pico-pi board running kernel
5.10.37 and I noticed that the firmware takes a long time to load
(more than 3 minutes after boot):

[  192.544227] ath10k_sdio mmc1:0001:1: qca9377 hw1.1 sdio target
0x05020001 chip_id 0x00000000 sub 0000:0000
[  192.554451] ath10k_sdio mmc1:0001:1: kconfig debug 0 debugfs 0
tracing 0 dfs 0 testmode 0
[  192.566465] ath10k_sdio mmc1:0001:1: firmware ver
WLAN.TF.1.1.1-00061-QCATFSWPZ-1 api 5 features ignore-otp crc32
7746e551
[  192.765756] ath10k_sdio mmc1:0001:1: failed to fetch board data for
bus=sdio,vendor=0271,device=0701,subsystem-vendor=0000,subsystem-device=0000
from ath10k/QCA9377/hw1.0/board-2.bin
[  192.784424] ath10k_sdio mmc1:0001:1: board_file api 1 bmi_id N/A
crc32 544289f7
[  194.081698] ath10k_sdio mmc1:0001:1: htt-ver 3.32 wmi-op 4 htt-op 3
cal otp max-sta 32 raw 0 hwcrypto 1
[  194.160101] mmc1: queuing unknown CIS tuple 0x01 (3 bytes)
[  194.177321] mmc1: queuing unknown CIS tuple 0x1a (5 bytes)
[  194.187873] mmc1: queuing unknown CIS tuple 0x1b (8 bytes)
[  194.194279] mmc1: queuing unknown CIS tuple 0x14 (0 bytes)

And then when I try to use it the following RCU messages are seen:

# wpa_supplicant  -iwlan0 -c /etc/wpa.conf &
# Successfully initialized wpa_supplicant
[  234.360447] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #08!!!
[  234.390478] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #08!!!
[  234.409903] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #08!!!
[  234.461811] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #08!!!
[  234.513919] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #08!!!
[  234.566124] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #08!!!
[  234.669870] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #08!!!
[  234.721845] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #08!!!
[  234.773752] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #08!!!
[  234.877801] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #08!!!
wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN

# wlan0: SME: Trying to authenticate wit[  239.203438] wlan0:
authenticate with xx:xx:xx:xx:xx:xx
h d4:b9:2f:2a:f8:64 (SSID='FABIOHOUSE' freq=2412 MHz)
[  239.264154] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[  239.280319] wlan0: authenticated
wlan0: Trying to associate with xx:xx:xx:xx:xx:xx(SSID='FABIOHOUSE'
freq=2412 MHz)
[  239.296632] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3)
[  239.309133] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx(capab=0x411
status=0 aid=4)
[  239.336270] wlan0: associated
wlan0: Associated with xx:xx:xx:xx:xx:xx
wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlan0: WPA: Key negotiation completed
[  239.553262] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=CCMP]
wlan0: CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx:xx
completed [id=0 id_str=]

Despite the two problems reported above the Wifi connection works:

# udhcpc -i wlan0
udhcpc: started, v1.33.0
udhcpc: sending discover
udhcpc: sending select for 192.168.0.19
udhcpc: lease of 192.168.0.19 obtained, lease time 86400
deleting routers
adding dns x.y.z.w
adding dns x.y.z.w

# ping google.com
PING google.com (172.217.29.110): 56 data bytes
64 bytes from a.b.c.d: seq=0 ttl=113 time=27.756 ms
64 bytes from a.b.c.d: seq=1 ttl=113 time=32.397 ms
64 bytes from a.b.c.d: seq=2 ttl=113 time=31.407 ms
64 bytes from a.b.c.d seq=3 ttl=113 time=30.491 ms

Does anyone have any suggestions for fixing these two issues? I have
also tested 5.12.4 with the same results. Using the QCA9377 firmware
from the latest linux-firmware tree.

Thanks,

Fabio Estevam

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: ath10k_sdio: Long time for loading firmware and RCU errors
  2021-05-26  0:40 ath10k_sdio: Long time for loading firmware and RCU errors Fabio Estevam
@ 2021-06-02 22:51 ` Fabio Estevam
  0 siblings, 0 replies; 2+ messages in thread
From: Fabio Estevam @ 2021-06-02 22:51 UTC (permalink / raw)
  To: Christian Hewitt, Gary Bisson, gerg, erik.stromdahl, Kalle Valo
  Cc: linux-wireless, ath10k

On Tue, May 25, 2021 at 9:40 PM Fabio Estevam <festevam@gmail.com> wrote:
>
> Hi,
>
> I am using the QCA9377 chip on an imx6dl-pico-pi board running kernel
> 5.10.37 and I noticed that the firmware takes a long time to load
> (more than 3 minutes after boot):

Ok, I replaced eudev with mdev in Buildroot and now it loads the
QCA9377 firmware quickly.

> # wpa_supplicant  -iwlan0 -c /etc/wpa.conf &
> # Successfully initialized wpa_supplicant
> [  234.360447] NOHZ tick-stop error: Non-RCU local softirq work is
> pending, handler #08!!!
> [  234.390478] NOHZ tick-stop error: Non-RCU local softirq work is
> pending, handler #08!!!

These NOHZ messages still pop up.

Cheers

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-06-02 22:52 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-05-26  0:40 ath10k_sdio: Long time for loading firmware and RCU errors Fabio Estevam
2021-06-02 22:51 ` Fabio Estevam

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).