From: Fabio Estevam <festevam@gmail.com> To: Kalle Valo <kvalo@codeaurora.org>, "Paul E . McKenney" <paulmck@kernel.org> Cc: ath10k@lists.infradead.org, linux-mmc <linux-mmc@vger.kernel.org>, Ulf Hansson <ulf.hansson@linaro.org>, Marek Vasut <marex@denx.de> Subject: NOHZ tick-stop error with ath10k SDIO Date: Wed, 18 Aug 2021 12:18:25 -0300 [thread overview] Message-ID: <CAOMZO5AAvZic-NFbYYSVfOxY-27QukXMX68f9eDmhbqAkBRKRw@mail.gmail.com> (raw) Hi, When launching the hostapd application on a i.MX7 based board with an ath10k device connected via SDIO, the following "NOHZ tick-stop error" messages are seen: # hostapd /etc/wifi.conf Configuration file: /etc/wifi.conf wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE [ 63.021149] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! Using interface wlan0 with hwaddr 00:1f:7b:31:04:a0 and ssid "thessid" [ 67.332470] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: interface state COUNTRY_UPDATE->ENABLED wlan0: AP-ENABLED [ 68.025845] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 69.025973] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 69.607432] cfg80211: failed to load regulatory.db [ 72.026748] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 73.027039] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 74.027159] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 75.027109] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 76.027461] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 77.027391] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 78.027560] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! This happens on all kernel versions from 5.10 to 5.13. Any ideas on how to fix this problem? Thanks, Fabio Estevam _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Fabio Estevam <festevam@gmail.com> To: Kalle Valo <kvalo@codeaurora.org>, "Paul E . McKenney" <paulmck@kernel.org> Cc: ath10k@lists.infradead.org, linux-mmc <linux-mmc@vger.kernel.org>, Ulf Hansson <ulf.hansson@linaro.org>, Marek Vasut <marex@denx.de> Subject: NOHZ tick-stop error with ath10k SDIO Date: Wed, 18 Aug 2021 12:18:25 -0300 [thread overview] Message-ID: <CAOMZO5AAvZic-NFbYYSVfOxY-27QukXMX68f9eDmhbqAkBRKRw@mail.gmail.com> (raw) Hi, When launching the hostapd application on a i.MX7 based board with an ath10k device connected via SDIO, the following "NOHZ tick-stop error" messages are seen: # hostapd /etc/wifi.conf Configuration file: /etc/wifi.conf wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE [ 63.021149] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! Using interface wlan0 with hwaddr 00:1f:7b:31:04:a0 and ssid "thessid" [ 67.332470] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: interface state COUNTRY_UPDATE->ENABLED wlan0: AP-ENABLED [ 68.025845] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 69.025973] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 69.607432] cfg80211: failed to load regulatory.db [ 72.026748] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 73.027039] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 74.027159] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 75.027109] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 76.027461] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 77.027391] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! [ 78.027560] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!! This happens on all kernel versions from 5.10 to 5.13. Any ideas on how to fix this problem? Thanks, Fabio Estevam
next reply other threads:[~2021-08-18 15:18 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-18 15:18 Fabio Estevam [this message] 2021-08-18 15:18 ` NOHZ tick-stop error with ath10k SDIO Fabio Estevam 2021-08-18 15:43 ` Paul E. McKenney 2021-08-18 15:43 ` Paul E. McKenney 2021-08-18 16:29 ` Fabio Estevam 2021-08-18 16:29 ` Fabio Estevam 2021-08-18 17:02 ` Fabio Estevam 2021-08-18 17:02 ` Fabio Estevam 2021-08-18 17:56 ` Paul E. McKenney 2021-08-18 17:56 ` Paul E. McKenney 2021-08-19 13:24 ` Fabio Estevam 2021-08-19 13:24 ` Fabio Estevam 2021-09-02 21:51 ` Thomas Gleixner 2021-09-02 21:51 ` Thomas Gleixner 2021-09-02 22:09 ` Paul E. McKenney 2021-09-02 22:09 ` Paul E. McKenney 2021-09-03 8:07 ` Thomas Gleixner 2021-09-03 8:07 ` Thomas Gleixner 2021-09-04 21:10 ` Fabio Estevam 2021-09-04 21:10 ` Fabio Estevam 2021-09-05 13:00 ` Thomas Gleixner 2021-09-05 13:00 ` Thomas Gleixner 2021-09-05 13:07 ` Fabio Estevam 2021-09-05 13:07 ` Fabio Estevam 2021-09-17 16:32 ` Qais Yousef 2021-09-17 16:32 ` Qais Yousef 2021-09-17 17:09 ` Paul E. McKenney 2021-09-17 17:09 ` Paul E. McKenney
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=CAOMZO5AAvZic-NFbYYSVfOxY-27QukXMX68f9eDmhbqAkBRKRw@mail.gmail.com \ --to=festevam@gmail.com \ --cc=ath10k@lists.infradead.org \ --cc=kvalo@codeaurora.org \ --cc=linux-mmc@vger.kernel.org \ --cc=marex@denx.de \ --cc=paulmck@kernel.org \ --cc=ulf.hansson@linaro.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.