[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aIrJipeLsGUM92+R@xsang-OptiPlex-9020>
Date: Thu, 31 Jul 2025 09:40:26 +0800
From: Oliver Sang <oliver.sang@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>
CC: Peter Zijlstra <peterz@...radead.org>, <oe-lkp@...ts.linux.dev>,
<lkp@...el.com>, <linux-kernel@...r.kernel.org>, <x86@...nel.org>, "Sebastian
Andrzej Siewior" <bigeasy@...utronix.de>, <linux-mm@...ck.org>,
<ltp@...ts.linux.it>, <oliver.sang@...el.com>
Subject: Re: [tip:locking/futex] [futex] 56180dd20c:
BUG:sleeping_function_called_from_invalid_context_at_kernel/nsproxy.c
hi, Thomas Gleixner,
On Tue, Jul 29, 2025 at 09:27:56AM +0200, Thomas Gleixner wrote:
> Oliver!
>
> On Tue, Jul 29 2025 at 08:22, Oliver Sang wrote:
> > On Fri, Jul 25, 2025 at 05:45:04PM +0200, Thomas Gleixner wrote:
> >> Can you please enable CONFIG_PREEMPT_TRACER and add
> >>
> >> 'trace_event=preemptirq:preempt_disable,preemptirq:preempt_enable ftrace_dump_on_oops'
> >>
> >> to the kernel command line. The latter will dump the recorded
> >> preempt_enable/disable events and we can pinpoint the function which is
> >> responsible for that.
> >
> > the config with CONFIG_PREEMPT_TRACER enabled is attached as
> > config-6.16.0-rc5-00002-g56180dd20c19
> >
> > by this config, we still see random
> > WARNING:at_kernel/sched/core.c:#preempt_count_sub
> ...
> > but bot seems not be able to capture other new dmesg stats.
>
> Ah. The tracer does not dump on warnings by default. You need
> 'panic_on_warn' on the command line as well. Forgot about that earlier.
attached one dmesg FYI.
>
> Thanks,
>
> tglx
>
Download attachment "dmesg-panic.xz" of type "application/x-xz" (2246696 bytes)
Powered by blists - more mailing lists