From: Fabio Estevam <festevam@gmail.com>
To: Christian Hewitt <christianshewitt@gmail.com>,
Gary Bisson <gary.bisson@boundarydevices.com>,
gerg@kernel.org, erik.stromdahl@gmail.com,
Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
ath10k@lists.infradead.org
Subject: Re: ath10k_sdio: Long time for loading firmware and RCU errors
Date: Wed, 2 Jun 2021 19:51:29 -0300 [thread overview]
Message-ID: <CAOMZO5A3csY5GkczjXWeec188vUr08kWDnY-miv=9OU8pDToBw@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5DPAr0XPHefewjF2fx7UL+7RvycAYLZdfosOUT6bwWHBA@mail.gmail.com>
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
prev parent reply other threads:[~2021-06-02 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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='CAOMZO5A3csY5GkczjXWeec188vUr08kWDnY-miv=9OU8pDToBw@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=christianshewitt@gmail.com \
--cc=erik.stromdahl@gmail.com \
--cc=gary.bisson@boundarydevices.com \
--cc=gerg@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
/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).