[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <73b5657a-4c47-980a-e709-cd6a880c067c@suse.cz>
Date: Fri, 14 Apr 2023 15:56:08 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: John Ogness <john.ogness@...utronix.de>,
Pierre Gondois <pierre.gondois@....com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>,
linux-rt-users@...r.kernel.org,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [ANNOUNCE] v6.3-rc2-rt3
On 4/14/23 15:49, John Ogness wrote:
> Hi Pierre,
>
> On 2023-04-14, Pierre Gondois <pierre.gondois@....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
Powered by blists - more mailing lists