linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anders Roxell <anders.roxell@linaro.org>
To: Tony Lindgren <tony@atomide.com>
Cc: rsalveti@rsalveti.net, John Stultz <john.stultz@linaro.org>,
	linux-wireless@vger.kernel.org, Eyal Reizer <eyalr@ti.com>
Subject: Re: wlcore getting stuck on hikey after the runtime PM autosuspend support change
Date: Mon, 17 Dec 2018 10:36:24 +0100	[thread overview]
Message-ID: <CADYN=9JEpTj444+SD_0fmBzK1DjRgSK-1S0ujeUyxXpuq6rLMA@mail.gmail.com> (raw)
In-Reply-To: <20181212183348.GI39861@atomide.com>

On Wed, 12 Dec 2018 at 19:33, Tony Lindgren <tony@atomide.com> wrote:
>
> * Anders Roxell <anders.roxell@linaro.org> [181211 23:45]:
> > I have different serious, one when our board hangs on udhcpc [1], then I see
> > wlcore and wl18xx_driver.
>
> Hmm so on what SoC is this with?

I'm sorry for the late reply. The Soc is Kirin 620.

Cheers,
Anders

> Adding Eyeal to Cc here too.
>
> Regards,
>
> Tony
>
> > [    8.824419] cfg80211: Loading compiled-in X.509 certificates for
> > regulatory database
> > [    8.852546] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
> > [    8.861006] platform regulatory.0: Direct firmware load for
> > regulatory.db failed with error -2
> > [    8.870248] cfg80211: failed to load regulatory.db
> > [    8.895501] asix 1-1.1:1.0 eth0: register 'asix' at
> > usb-f72c0000.usb-1.1, ASIX AX88772B USB 2.0 Ethernet,
> > 00:50:b6:14:c8:76
> > [    8.912285] usbcore: registered new interface driver asix
> > [    9.053373] mmc_host mmc2: Bus speed (slot 0) = 24800000Hz (slot
> > req 100000Hz, actual 100000HZ div = 124)
> > [    9.130886] mmc_host mmc2: Bus speed (slot 0) = 24800000Hz (slot
> > req 25000000Hz, actual 24800000HZ div = 0)
> > [    9.149318] wl18xx_driver wl18xx.3.auto: Direct firmware load for
> > ti-connectivity/wl18xx-conf.bin failed with error -2
> > [    9.160459] wlcore: ERROR could not get configuration binary
> > ti-connectivity/wl18xx-conf.bin: -2
> > [    9.169615] wlcore: WARNING falling back to default config
> > [    9.214108] mmc_host mmc2: Bus speed (slot 0) = 24800000Hz (slot
> > req 100000Hz, actual 100000HZ div = 124)
> > [    9.294294] mmc_host mmc2: Bus speed (slot 0) = 24800000Hz (slot
> > req 25000000Hz, actual 24800000HZ div = 0)
> > [[0;32m  OK  [0m] Listening on Load/Save RF Kill Switch Status
> > /dev/rfkill Watch.
> > [[0;32m  OK  [0m] Reached target Sockets.
> > [[0;32m  OK  [0m] Reached target Basic System.
> >          Starting Entropy Daemon based on the HAVEGE algorithm...
> > [[0;32m  OK  [0m] Started TEE Supplicant.
> > [    9.514713] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
> > [    9.526319] wlcore: WARNING Detected unconfigured mac address in
> > nvs, derive from fuse instead.
> > [    9.535454] wlcore: WARNING This default nvs file can be removed
> > from the file system
> >
> > and when it passes that stage I can't find wlcore nor wl18xx_driver.
> > However, I can see
> > wl1271_sdio failing instead. See [2]
> >
> > [    8.435849] Bluetooth: HCI UART protocol Broadcom registered
> > [    8.439669] mmc_host mmc2: Bus speed (slot 0) = 24800000Hz (slot
> > req 200000Hz, actual 200000HZ div = 62)
> > [[0;32m  OK  [0m] Started dnf-automatic-download timer.
> > [    8.469492] wl1271_sdio: probe of mmc2:0001:2 failed with error -16
> > [[0;32m  OK  [0m] Started Daily Cleanup of Temporary Directories.
> > [[0;32m  OK  [0m] Started dnf-automatic-install timer.
> > [    8.525443] Console: switching to colour frame buffer device 256x72
> > [    8.533489] Bluetooth: hci0: change remote baud rate command in firmware
> > [    8.584607] kirin-drm f4100000.ade: fb0: DRM emulated frame buffer device
> > [[0;32m  OK  [0m] Started dnf-automatic-notifyonly timer.
> > [[0;32m  OK  [0m] Listening on R[    8.614417] [drm] Initialized kirin
> > 1.0.0 20150718 for f4100000.ade on minor 0
> >
> > and another job that have the similar issue with the previous is [3]:
> >
> > [    8.670110] adv7511 2-0039: 2-0039 supply pvdd not found, using
> > dummy regulator
> > [    8.677908] adv7511 2-0039: 2-0039 supply a2vdd not found, using
> > dummy regulator
> > [    8.685788] adv7511 2-0039: 2-0039 supply v3p3 not found, using
> > dummy regulator
> > [    8.688699] wl1271_sdio: probe of mmc2:0001:1 failed with error -16
> > [    8.690154] Bluetooth: Core ver 2.22
> > [    8.690346] NET: Registered protocol family 31
> > [    8.690355] Bluetooth: HCI device and connection manager
> > initialized
> > [    8.693495] adv7511 2-0039: 2-0039 supply v1p2 not found, using
> > dummy regulator
> > [    8.700240] wl1271_sdio: probe of mmc2:0001:2 failed with error -16
> > [    8.700992] Bluetooth: HCI socket layer initialized
> > [    8.701022] Bluetooth: L2CAP socket layer initialized
> > [    8.701554] Bluetooth: SCO socket layer initialized
> >              Starting sshd.socket.
> > [[0;32m  OK  [0m] Listening on RPCbind Server Activation Socket.
> > [[0;32m  OK  [0m] Started Daily rotation of log files.
> > [    8.791540] Bluetooth: HCI UART driver ver 2.3
> >
> >
> > I'm confused why we only see wlcore wl18xx in job [1] and that we see wl1271
> > in the other and that we are able to start running tests, even though
> > I don't think
> > the jobs where we run tests booted up OK, since we can see
> > "wl1271_sdio: probe of mmc2:0001:1 failed with error -16".
> >
> > Cheers,
> > Anders
> >
> > [1] https://lkft.validation.linaro.org/scheduler/job/543012
> > [2] https://lkft.validation.linaro.org/scheduler/job/506683
> > [3] https://lkft.validation.linaro.org/scheduler/job/487494

  reply	other threads:[~2018-12-17  9:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 18:06 wlcore getting stuck on hikey after the runtime PM autosuspend support change Ricardo Salveti
2018-12-11 18:19 ` Tony Lindgren
2018-12-11 18:52   ` Ricardo Salveti
2018-12-11 19:01     ` Tony Lindgren
2018-12-11 19:25       ` Ricardo Salveti
2018-12-11 19:50         ` John Stultz
2018-12-11 20:12           ` Tony Lindgren
2018-12-11 20:23             ` Ricardo Salveti
2018-12-11 20:44               ` Ricardo Salveti
2018-12-12  1:45                 ` Tony Lindgren
2018-12-12  7:27                   ` [EXTERNAL] " Reizer, Eyal
2018-12-12 18:31                     ` Tony Lindgren
2018-12-12 19:24                       ` Ricardo Salveti
2018-12-13  7:49                         ` Reizer, Eyal
2018-12-13 13:52                           ` Ricardo Salveti
2018-12-13 14:45                             ` Tony Lindgren
2018-12-13 14:53                               ` Reizer, Eyal
2018-12-13 14:55                                 ` Ricardo Salveti
2018-12-14 20:41                               ` Ricardo Salveti
2018-12-14 23:28                                 ` Tony Lindgren
2018-12-15  3:37                                   ` Ricardo Salveti
2018-12-17 14:45                                     ` Tony Lindgren
2018-12-12 19:16                     ` Ricardo Salveti
2018-12-11 21:50               ` Ricardo Salveti
2018-12-11 23:44                 ` Anders Roxell
2018-12-12 18:33                   ` Tony Lindgren
2018-12-17  9:36                     ` Anders Roxell [this message]
2018-12-12  1:25                 ` Tony Lindgren
2018-12-12 19:20                   ` Ricardo Salveti
2018-12-11 19:13 ` John Stultz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADYN=9JEpTj444+SD_0fmBzK1DjRgSK-1S0ujeUyxXpuq6rLMA@mail.gmail.com' \
    --to=anders.roxell@linaro.org \
    --cc=eyalr@ti.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rsalveti@rsalveti.net \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).