netdev - Re: Long Delay on startup of wl18xx Wireless chip

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 5 Nov 2019 20:24:15 +0100
From:   "H. Nikolaus Schaller" <hns@...delico.com>
To:     Adam Ford <aford173@...il.com>
Cc:     Linux-OMAP <linux-omap@...r.kernel.org>, kvalo@...eaurora.org,
        "David S . Miller" <davem@...emloft.net>,
        linux-wireless@...r.kernel.org, netdev <netdev@...r.kernel.org>
Subject: Re: Long Delay on startup of wl18xx Wireless chip

Hi Adam,

> Am 05.11.2019 um 19:55 schrieb Adam Ford <aford173@...il.com>:
> 
> On Tue, Nov 5, 2019 at 12:25 PM Adam Ford <aford173@...il.com> wrote:
>> 
>> I am seeing a really long delay at startup of the wl18xx using the 5.4 kernel.
>> 
> 
> Sorry I had to resend.  I forgot to do plaintext.  Google switched
> settings on me and neglected to inform me.
> 
> 
>> [    7.895551] wl18xx_driver wl18xx.2.auto: Direct firmware load for ti-connectivity/wl18xx-conf.bin failed with error -2
>> [    7.906416] wl18xx_driver wl18xx.2.auto: Falling back to sysfs fallback for: ti-connectivity/wl18xx-conf.bin
>> 
>> At this point in the sequence, I can login to Linux, but the WL18xx is unavailable.
>> 
>> [   35.032382] vwl1837: disabling
>> [   69.594874] wlcore: ERROR could not get configuration binary ti-connectivity/wl18xx-conf.bin: -11
>> [   69.604013] wlcore: WARNING falling back to default config
>> [   70.174821] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
>> [   70.189003] wlcore: WARNING Detected unconfigured mac address in nvs, derive from fuse instead.
>> [   70.197851] wlcore: WARNING This default nvs file can be removed from the file system
>> [   70.218816] wlcore: loaded
>> 
>> It is now at this point when the wl18xx is available.
>> 
>> I have the wl18xx and wlcore setup as a module so it should load after the filesystem is mounted.  I am not using a wl18xx-conf.bin, but I never needed to use this before.
>> 
>> It seems to me unreasonable to wait 60+ seconds after everything is mounted for the wireless chip to become available.  Before I attempt to bisect this, I was hoping someone might have seen this.  I am also trying to avoid duplicating someone else's efforts.
>> 
>> I know the 4.19 doesn't behave like this.

I have with v5.4-rc6 on omap5 + wl1835

root@...ux:~# dmesg|fgrep wlcore
[   10.268847] wl18xx_driver wl18xx.0.auto: Direct firmware load for ti-connectivity/wl18xx-conf.bin failed with error -2
[   10.291610] wlcore: ERROR could not get configuration binary ti-connectivity/wl18xx-conf.bin: -2
[   10.303839] wlcore: WARNING falling back to default config
[   10.700055] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[   10.703469] wlcore: WARNING Detected unconfigured mac address in nvs, derive from fuse instead.
[   10.703478] wlcore: WARNING This default nvs file can be removed from the file system
[   12.738721] wlcore: loaded
[   13.978498] wlcore: PHY firmware version: Rev 8.2.0.0.237
[   14.073765] wlcore: firmware booted (Rev 8.9.0.0.70)
[   14.096806] wlcore: down
[   14.589917] wlcore: PHY firmware version: Rev 8.2.0.0.237
[   14.693183] wlcore: firmware booted (Rev 8.9.0.0.70)
root@...ux:~# 

Hope this helps.

BR,
Nikolaus