Thanks for the hints. I did some experiments with increasing the
startup-delay-us of wl12xx_vmmc2 but couldn't notice any effect.
I also tried other changes in the device tree, kernel command line
arguments and kernel configuration, but I can't see any pattern in the
result. Whatever I try the initialization very often still fails with
errors as before. Occasionally I even get crashes such as:
[ 7.188934] mmc1: tried to HW reset card, got error -110
sysctl: cannot stat /proc/sys/net/ipv4/tcp_syncookies: No such file or directory
[ 7.410125] ------------[ cut here ]------------
[ 7.414825] WARNING: CPU: 0 PID: 10 at drivers/net/wireless/ti/wlcore/sdio.c:131 wl12xx_sdio_raw_write+0xa3/0x104 [wlcore_sdio]
[ 7.426422] Modules linked in: wl12xx wlcore mac80211 libarc4 omapdrm sha256_generic libsha256 drm_kms_helper sha256_arm cfbfillrect syscopyarea cfbimgblt sysfillrect sysimgblt fb_sys_fops cfbcopyarea cfg80211 joydev mousedev evdc
[ 7.506774] CPU: 0 PID: 10 Comm: kworker/0:1 Not tainted 5.4.28-pte-g6f3bf13d53 #1
[ 7.514465] Hardware name: Generic OMAP36xx (Flattened Device Tree)
[ 7.520812] Workqueue: events request_firmware_work_func
[ 7.526214] [<c010c0c5>] (unwind_backtrace) from [<c0109863>] (show_stack+0xb/0xc)
[ 7.533905] [<c0109863>] (show_stack) from [<c0122541>] (__warn+0xb5/0xb8)
[ 7.540893] [<c0122541>] (__warn) from [<c01227a9>] (warn_slowpath_fmt+0x41/0x7c)
[ 7.548461] [<c01227a9>] (warn_slowpath_fmt) from [<bfa0a217>] (wl12xx_sdio_raw_write+0xa3/0x104 [wlcore_sdio])
[ 7.558807] [<bfa0a217>] (wl12xx_sdio_raw_write [wlcore_sdio]) from [<bfaf9e9b>] (wlcore_set_partition+0x83/0x340 [wlcore])
[ 7.570220] [<bfaf9e9b>] (wlcore_set_partition [wlcore]) from [<bfaf402d>] (wl12xx_set_power_on+0x4d/0xd4 [wlcore])
[ 7.580841] [<bfaf402d>] (wl12xx_set_power_on [wlcore]) from [<bfaf5ea9>] (wlcore_nvs_cb+0xdd/0x804 [wlcore])
[ 7.590942] [<bfaf5ea9>] (wlcore_nvs_cb [wlcore]) from [<c04328ad>] (request_firmware_work_func+0x35/0x64)
[ 7.600708] [<c04328ad>] (request_firmware_work_func) from [<c0132efb>] (process_one_work+0x117/0x30c)
[ 7.610168] [<c0132efb>] (process_one_work) from [<c01331d7>] (worker_thread+0xe7/0x388)
[ 7.618316] [<c01331d7>] (worker_thread) from [<c0136f89>] (kthread+0xed/0xf4)
[ 7.625640] [<c0136f89>] (kthread) from [<c01010f9>] (ret_from_fork+0x11/0x38)
[ 7.632965] Exception stack(0xcd199fb0 to 0xcd199ff8)
[ 7.638061] 9fa0: 00000000 00000000 00000000 00000000
[ 7.646331] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 7.654602] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 7.661285] ---[ end trace 09a18993a63ecdda ]---
[ 7.665954] wl1271_sdio mmc1:0001:2: sdio write failed (-110)
On 6/22/20 5:28 PM, Tony Lindgren wrote:
* Oskar Enoksson <enok@xxxxxxxxxxxxxx> [200621 22:01]:
Correction: occasionally wl1271_sdio initialization still fails with error
messages such as
[ 46.961364] wl1271_sdio: probe of mmc1:0001:1 failed with error -16
[ 46.967834] wl1271_sdio: probe of mmc1:0001:2 failed with error -16
other times
[ 27.302215][ T903] wl1271_sdio mmc1:0001:2: wl12xx_sdio_power_on: failed
to get_sync(-22)
or
root@pte2000:~# ifup wlan0
[ 53.799468][ T2420] wl1271_sdio mmc1:0001:2: wl12xx_sdio_power_on: failed
to get_sync(-110)
[ 53.840118][ T2420] wl1271_sdio mmc1:0001:2: wl12xx_sdio_power_on: failed
to get_sync(-22)
[ 53.879882][ T2420] wl1271_sdio mmc1:0001:2: wl12xx_sdio_power_on: failed
to get_sync(-22)
[ 53.888610][ T2420] wlcore: ERROR firmware boot failed despite 3 retries
RTNETLINK answers: Invalid argument
ifup: failed to bring up wlan0
Maybe try changing the wl12xx_vmmc2 startup-delay-us to something
higher like 70000 we usually have?
Regards,
Tony
