[Buildroot] EUDEV takes a very long time to load the Wifi firmware

[Buildroot] EUDEV takes a very long time to load the Wifi firmware

[Fabio Estevam]

Hi,

I am running kernel 5.12.4 on an imx6dl-pico-pi board with a QCA9377 Wifi chip.

Originally I was selecting BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y,
but that caused the QCA9377 firmware to be loaded only after almost 3
minutes.

Changing it to BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV=y caused the
QCA9377 firmware to be loaded very quickly as expected.

I am using a recent master version of Buildroot:
ab9ceea782c770acdb9a25d8601b12af261c8ccb

I am OK with using MDEV but just wanted to report it in case someone
knows if this is a known EUDEV issue.

Thanks,

Fabio Estevam

[Buildroot] EUDEV takes a very long time to load the Wifi firmware

[Peter Korsgaard]

>>>>> "Fabio" == Fabio Estevam <festevam@gmail.com> writes:

 > Hi,
 > I am running kernel 5.12.4 on an imx6dl-pico-pi board with a QCA9377 Wifi chip.

 > Originally I was selecting BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y,
 > but that caused the QCA9377 firmware to be loaded only after almost 3
 > minutes.

 > Changing it to BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV=y caused the
 > QCA9377 firmware to be loaded very quickly as expected.

 > I am using a recent master version of Buildroot:
 > ab9ceea782c770acdb9a25d8601b12af261c8ccb

 > I am OK with using MDEV but just wanted to report it in case someone
 > knows if this is a known EUDEV issue.

Is there anything of interest in the logs? The eudev init script runs
udevadm settle, does that take a long time or perhaps even times out?

-- 
Bye, Peter Korsgaard

[Buildroot] EUDEV takes a very long time to load the Wifi firmware

[Fabio Estevam]

Hi Peter,

On Thu, Jun 3, 2021 at 3:20 AM Peter Korsgaard <peter@korsgaard.com> wrote:

> Is there anything of interest in the logs? The eudev init script runs
> udevadm settle, does that take a long time or perhaps even times out?

Unfortunately, no logs are shown. I only get the kernel-related
firmware loading messages:

[  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)

after more than 3 minutes as shown by the timestamp.

With mdev these same messages appear after 9 seconds.

Thanks

[Buildroot] EUDEV takes a very long time to load the Wifi firmware

[Michael Nazzareno Trimarchi]

Hi

On Thu, Jun 3, 2021 at 1:45 PM Fabio Estevam <festevam@gmail.com> wrote:

> Hi Peter,
>
> On Thu, Jun 3, 2021 at 3:20 AM Peter Korsgaard <peter@korsgaard.com>
> wrote:
>
> > Is there anything of interest in the logs? The eudev init script runs
> > udevadm settle, does that take a long time or perhaps even times out?
>
> Unfortunately, no logs are shown. I only get the kernel-related
> firmware loading messages:
>
> [  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)
>
>
You need to log eudev and increase log level. That show when sdio peripheral
is detected and we need a dmesg log

Michael

after more than 3 minutes as shown by the timestamp.
>
> With mdev these same messages appear after 9 seconds.
>
> Thanks
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>


-- 
Michael Nazzareno Trimarchi
Co-Founder & Chief Executive Officer
M. +39 347 913 2170
michael at amarulasolutions.com
__________________________________

Amarula Solutions BV
Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
T. +31 (0)85 111 9172
info at amarulasolutions.com
www.amarulasolutions.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210603/bfe1d842/attachment.html>