From: Vlastimil Babka <vbabka@suse.cz>
To: John Ogness <john.ogness@linutronix.de>,
Pierre Gondois <pierre.gondois@arm.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [ANNOUNCE] v6.3-rc2-rt3
Date: Fri, 14 Apr 2023 15:56:08 +0200 [thread overview]
Message-ID: <73b5657a-4c47-980a-e709-cd6a880c067c@suse.cz> (raw)
In-Reply-To: <87ttxiefpd.fsf@jogness.linutronix.de>
On 4/14/23 15:49, John Ogness wrote:
> Hi Pierre,
>
> On 2023-04-14, Pierre Gondois <pierre.gondois@arm.com> wrote:
>> =============================
>> [ BUG: Invalid wait context ]
>> 6.3.0-rc5-rt8-gacb52bd349a2 #417 Not tainted
>> -----------------------------
>> swapper/0/1 is trying to lock:
>> ffff00097eea1180 (cpu){....}-{3:3}, at: __printk_safe_enter (kernel/printk/printk_safe.c:28 (discriminator 3))
>> other info that might help us debug this:
>> context-{5:5}
>> 1 lock held by swapper/0/1:
>> #0: ffff80000ba77028 (rcu_tasks_rude.cbs_gbl_lock){....}-{2:2}, at: cblist_init_generic (kernel/rcu/tasks.h:233)
>
> This is actually a mainline issue relating to legacy consoles. In
> mainline you see it as a warning when CONFIG_PROVE_RAW_LOCK_NESTING is
> enabled.
>
> If you enable CONFIG_PREEMPT_RT you will not have the problem.
>
> I will look at how the issue can be gracefully ignored in
> !CONFIG_PREEMPT_RT.
Is it perhaps a similar situation to this thread?
https://lore.kernel.org/all/20230412124735.GE628377@hirez.programming.kicks-ass.net/
> Thanks for reporting.
>
> John Ogness
next prev parent reply other threads:[~2023-04-14 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 17:05 Sebastian Andrzej Siewior
2023-03-14 17:12 ` Sebastian Andrzej Siewior
2023-04-14 11:55 ` Pierre Gondois
2023-04-14 13:49 ` John Ogness
2023-04-14 13:56 ` Vlastimil Babka [this message]
2023-04-14 15:01 ` John Ogness
2023-04-14 15:38 ` Vlastimil Babka
2023-04-18 15:08 ` 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=73b5657a-4c47-980a-e709-cd6a880c067c@suse.cz \
--to=vbabka@suse.cz \
--cc=bigeasy@linutronix.de \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pierre.gondois@arm.com \
--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
all inboxes | Powered by JetHome®