From: Francesco Dolcini <francesco@dolcini.it>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Francesco Dolcini <francesco@dolcini.it>,
Vignesh Raghavendra <vigneshr@ti.com>,
Amitkumar Karwar <amitkumar.karwar@nxp.com>,
Neeraj Kale <neeraj.sanjaykale@nxp.com>,
Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>
Subject: Re: Kernel WARNING (RCU) with btnxpuart on TI AM62 platform
Date: Fri, 23 May 2025 10:07:32 +0200 [thread overview]
Message-ID: <20250523080732.GA19643@francesco-nb> (raw)
In-Reply-To: <4286c852-c5c5-468b-a8f5-fc226e71d5e9@molgen.mpg.de>
On Mon, May 12, 2025 at 04:47:28PM +0200, Paul Menzel wrote:
> Am 10.04.25 um 08:20 schrieb Francesco Dolcini:
> > On Tue, Apr 08, 2025 at 09:15:26PM +0530, Vignesh Raghavendra wrote:
> > > On 08/04/25 14:05, Francesco Dolcini wrote:
> > > > I do have the following kernel warning with 6.15-rc1, on a TI AM62
> > > > platform (arm64), single CPU core, using btnxpuart driver, any idea?
> > > > PREEMPT_RT is enabled, if it matters.
> > > >
> > > > Either the issue is not systematic, or multi cores SoCs are not affected
> > > > (no error on the exact same image on a dual nor on quad core TI AM62).
...
> Not that this gets forgotten. Vignesh, is your theory still valid with
> PREEMPT_RT not set?
>
> Francesco, were you able to test older Linux kernels in the meantime?
Yes. The same happens with 6.12.30 kernel. Not systematic.
[ 19.908418] Voluntary context switch within RCU read-side critical section!
[ 19.908453] WARNING: CPU: 0 PID: 371 at /kernel/rcu/tree_plugin.h:331 rcu_note_context_switch+0x3d0/0x428
[ 19.908510] Modules linked in: sd_mod uas onboard_usb_dev optee_rng rng_core btnxpuart dwc3 evdev spidev aes_ce_blk aes_ce_cipher ghash_ce gf128mul sha2_ce sha256_arm64 sha1_ce snd_soc_simple_card snd_soc_simple_card_utils display_connector optee gpio_keys spi_cadence_quadspi usb_conn_gpio tee roles k3_j72xx_bandgap mwifiex_sdio mwifiex cfg80211 rtc_ti_k3 dwc3_am62 bluetooth ecdh_generic ecc sa2ul rfkill sha512_generic authenc tidss snd_soc_davinci_mcasp crypto_null libaes snd_soc_ti_udma drm_display_helper snd_soc_ti_edma sha1_generic snd_soc_ti_sdma omap_hwspinlock ti_ads1015 lontium_lt8912b ina2xx industrialio_triggered_buffer kfifo_buf tps65219_pwrbutton tc358768 lm75 m_can_platform snd_soc_wm8904 pwm_tiehrpwm m_can can_dev spi_omap2_mcspi fuse ipv6 autofs4
[ 19.908761] CPU: 0 UID: 0 PID: 371 Comm: kworker/u5:2 Not tainted 6.12.30-7.3.0-devel #1
[ 19.908773] Hardware name: Toradex Verdin AM62 WB on Dahlia Board (DT)
[ 19.908780] Workqueue: hci0 hci_power_off [bluetooth]
[ 19.908917] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 19.908930] pc : rcu_note_context_switch+0x3d0/0x428
[ 19.908946] lr : rcu_note_context_switch+0x3d0/0x428
[ 19.908957] sp : ffff8000825dba60
[ 19.908961] x29: ffff8000825dba60 x28: 0000000000000000 x27: 0000000000000000
[ 19.908977] x26: ffff0000011e11c0 x25: ffff00000a5a9080 x24: 0000000000000000
[ 19.908988] x23: 0000000000000000 x22: ffff00000a5a9080 x21: ffff00001daa92c0
[ 19.908999] x20: ffff8000810220c0 x19: ffff00001daaa0c0 x18: fffffffffffe7a38
[ 19.909010] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000048
[ 19.909023] x14: fffffffffffe7a80 x13: 216e6f6974636573 x12: 206c616369746972
[ 19.909034] x11: 6320656469732d64 x10: 6165722055435220 x9 : 206e696874697720
[ 19.909045] x8 : 6863746977732074 x7 : ffff80008122c840 x6 : ffff8000825db820
[ 19.909056] x5 : ffff00001da9f888 x4 : 0000000000000000 x3 : 0000000000000027
[ 19.909071] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff00000a5a9080
[ 19.909084] Call trace:
[ 19.909089] rcu_note_context_switch+0x3d0/0x428
[ 19.909107] __schedule+0x98/0x774
[ 19.909124] schedule+0x34/0x104
[ 19.909133] rpm_resume+0x17c/0x6b0
[ 19.909144] __pm_runtime_resume+0x48/0x88
[ 19.909158] serial8250_stop_rx+0x28/0x84
[ 19.909173] uart_tty_port_shutdown+0x3c/0x178
[ 19.909184] tty_port_shutdown+0x84/0xdc
[ 19.909201] tty_port_close+0x3c/0xac
[ 19.909211] uart_close+0x34/0x98
[ 19.909219] ttyport_close+0x50/0x94
[ 19.909230] serdev_device_close+0x40/0x50
[ 19.909243] btnxpuart_close+0x1c/0x9c [btnxpuart]
[ 19.909258] hci_dev_close_sync+0x314/0x7d8 [bluetooth]
[ 19.909325] hci_dev_do_close+0x2c/0x70 [bluetooth]
[ 19.909388] hci_power_off+0x20/0x64 [bluetooth]
[ 19.909454] process_one_work+0x148/0x28c
[ 19.909477] worker_thread+0x2d4/0x3d8
[ 19.909488] kthread+0x110/0x114
[ 19.909499] ret_from_fork+0x10/0x20
[ 19.909518] ---[ end trace 0000000000000000 ]---
Francesco
prev parent reply other threads:[~2025-05-23 8:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 8:35 Kernel WARNING (RCU) with btnxpuart on TI AM62 platform Francesco Dolcini
2025-04-08 9:26 ` Paul Menzel
2025-04-08 9:35 ` Francesco Dolcini
2025-04-08 15:45 ` Vignesh Raghavendra
2025-04-10 6:20 ` Francesco Dolcini
2025-04-10 6:34 ` Paul Menzel
2025-04-10 6:48 ` Paul Menzel
2025-04-10 6:51 ` Paul Menzel
2025-04-10 9:53 ` Francesco Dolcini
2025-05-12 14:47 ` Paul Menzel
2025-05-23 8:07 ` Francesco Dolcini [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=20250523080732.GA19643@francesco-nb \
--to=francesco@dolcini.it \
--cc=amitkumar.karwar@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=neeraj.sanjaykale@nxp.com \
--cc=nm@ti.com \
--cc=pmenzel@molgen.mpg.de \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.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