public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Gondois <pierre.gondois@arm.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v6.6-rc4-rt7
Date: Thu, 5 Oct 2023 15:38:06 +0200	[thread overview]
Message-ID: <375571ff-c63e-9045-81ff-dc93bcade8ee@arm.com> (raw)
In-Reply-To: <20231004160655.0D-7XFo_@linutronix.de>

Hello Sebastian,
The following happened once [1]. In pl011_console_write() from:
   commit da042bbb7a3f ("printk: Update the printk series.")
&uap->port seems to be released, but various paths don't seem
to acquire the lock,

Regards,
Pierre

[1]
[...] =====================================
[...] WARNING: bad unlock balance detected!
[...] 6.6.0-rc4-rt7-00098-g400db4a2dd90 #1157 Not tainted
[...] -------------------------------------
[...] pr/legacy/18 is trying to release lock (&port_lock_key) at:
[...] pl011_console_write ([path]/drivers/tty/serial/amba-pl011.c:2366)
[...] but there are no more locks to release!
[...]
[...] other info that might help us debug this:
[...] 2 locks held by pr/legacy/18:
[...] #0: ffff8000846bc0b8 (console_lock){+.+.}-{0:0}, at: nbcon_legacy_kthread_func ([path]/kernel/printk/printk.c:3052 [path]/kernel/printk/printk.c:3364)
[...] #1: ffff8000846bc030 (console_srcu){....}-{0:0}, at: console_flush_all ([path]/./include/linux/srcu.h:230 [path]/kernel/printk/printk.c:286 [path]/kernel/printk/printk.c:2971)
[...]
[...] stack backtrace:
[...] CPU: 1 PID: 18 Comm: pr/legacy Not tainted 6.6.0-rc4-rt7-00098-g400db4a2dd90 #1157
[...] Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform, BIOS EDK II Sep  5 2023
[...] Call trace:
[...] dump_backtrace ([path]/arch/arm64/kernel/stacktrace.c:235)
[...] show_stack ([path]/arch/arm64/kernel/stacktrace.c:242)
[...] dump_stack_lvl ([path]/lib/dump_stack.c:107)
[...] dump_stack ([path]/lib/dump_stack.c:114)
[...] print_unlock_imbalance_bug ([path]/kernel/locking/lockdep.c:5201)
[...] lock_release ([path]/kernel/locking/lockdep.c:5438 [path]/kernel/locking/lockdep.c:5780)
[...] rt_spin_unlock ([path]/kernel/locking/spinlock_rt.c:81)
[...] pl011_console_write ([path]/drivers/tty/serial/amba-pl011.c:2366)
[...] console_flush_all ([path]/kernel/printk/printk.c:2910 [path]/kernel/printk/printk.c:2992)
[...] nbcon_legacy_kthread_func ([path]/kernel/printk/printk.c:3053 [path]/kernel/printk/printk.c:3364)
[...] kthread ([path]/kernel/kthread.c:388)
[...] ret_from_fork ([path]/arch/arm64/kernel/entry.S:854)


On 10/4/23 18:06, Sebastian Andrzej Siewior wrote:
> Dear RT folks!
> 
> I'm pleased to announce the v6.6-rc4-rt7 patch set.
> 
> Changes since v6.6-rc4-rt6:
> 
>    - Lockdep complained about SRCU locking if printk was used from NMI.
> 
>    - The i915 driver could create a locking related splat during suspend/
>      resume. Reported by John B. Wyatt IV.
> 
>    - A new version of printk. This is an update to the current
>      development version. Large patch series provided by John Ogness.
> 
> Known issues
>       None
> 
> The delta patch against v6.6-rc4-rt6 is not appended below due to its
> size. It and can be found here:
>   
>       https://cdn.kernel.org/pub/linux/kernel/projects/rt/6.6/incr/patch-6.6-rc4-rt6-rt7.patch.xz
> 
> and as web based diff:
>       
>       https://git.kernel.org/rt/linux-rt-devel/d/v6.6-rc4-rt7/v6.6-rc4-rt6
> 
> You can get this release via the git tree at:
> 
>      https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git v6.6-rc4-rt7
> 
> The RT patch against v6.6-rc4 can be found here:
> 
>      https://cdn.kernel.org/pub/linux/kernel/projects/rt/6.6/older/patch-6.6-rc4-rt7.patch.xz
> 
> The split quilt queue is available at:
> 
>      https://cdn.kernel.org/pub/linux/kernel/projects/rt/6.6/older/patches-6.6-rc4-rt7.tar.xz
> 
> Sebastian
> 

  reply	other threads:[~2023-10-05 13:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 16:06 [ANNOUNCE] v6.6-rc4-rt7 Sebastian Andrzej Siewior
2023-10-05 13:38 ` Pierre Gondois [this message]
2023-10-05 14:17   ` Sebastian Andrzej Siewior
2023-10-10  9:23 ` Pierre Gondois
2023-10-18 14:30   ` Sebastian Andrzej Siewior

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=375571ff-c63e-9045-81ff-dc93bcade8ee@arm.com \
    --to=pierre.gondois@arm.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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