[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <874iusihka.ffs@tglx>
Date: Thu, 31 Jul 2025 16:03:01 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Oliver Sang <oliver.sang@...el.com>
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
On Thu, Jul 31 2025 at 14:34, Thomas Gleixner wrote:
> On Thu, Jul 31 2025 at 09:40, Oliver Sang wrote:
>> On Tue, Jul 29, 2025 at 09:27:56AM +0200, Thomas Gleixner wrote:
>>> > 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.
>
> Hmm, that trace dump was cut off before it completed by a reset
> (probably your test timeout).
>
> Either you make the timeout longer or try the following on the kernel
> command line instead of 'ftrace_dump_on_cpu':
instead of 'ftrace_dump_ooops'
obviously
Powered by blists - more mailing lists