[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87bjosenua.ffs@tglx>
Date: Wed, 06 Aug 2025 12:39:09 +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 Wed, Aug 06 2025 at 16:35, Oliver Sang wrote:
> On Wed, Aug 06, 2025 at 10:19:36AM +0200, Thomas Gleixner wrote:
>> Oliver!
>>
>> On Wed, Aug 06 2025 at 16:01, Oliver Sang wrote:
>> > On Thu, Jul 31, 2025 at 04:03:01PM +0200, Thomas Gleixner wrote:
>> >> On Thu, Jul 31 2025 at 14:34, Thomas Gleixner wrote:
>> >> > 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'
>> >
>> > sorry for late, I just took several-day off.
>>
>> I hope you had a good time!
>>
>> > attached dmesg FYI.
>>
>> Thanks for doing this. Now the buffer is too short and as nothing stops
>> the tracer the interesting stuff goes out of sight.
>>
>> Can you please apply the patch below and try again?
>
> got it!
>
> just want to confirm, still use below params or need some modification?
>
> trace_event=preemptirq:preempt_disable,preemptirq:preempt_enable ftrace_dump_on_oops=orig_cpu trace_buf_size=100K panic_on_warn=1
Those should be good. Let's see.
Powered by blists - more mailing lists