All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Oliver Sang <oliver.sang@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	linux-mm@kvack.org, ltp@lists.linux.it, oliver.sang@intel.com
Subject: Re: [tip:locking/futex] [futex]  56180dd20c: BUG:sleeping_function_called_from_invalid_context_at_kernel/nsproxy.c
Date: Tue, 29 Jul 2025 09:27:56 +0200	[thread overview]
Message-ID: <87wm7ro3r7.ffs@tglx> (raw)
In-Reply-To: <aIgUUhKWesDpM0BJ@xsang-OptiPlex-9020>

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.

Thanks,

        tglx


WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: Oliver Sang <oliver.sang@intel.com>
Cc: lkp@intel.com, Peter Zijlstra <peterz@infradead.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	oliver.sang@intel.com, oe-lkp@lists.linux.dev,
	ltp@lists.linux.it
Subject: Re: [LTP] [tip:locking/futex] [futex] 56180dd20c: BUG:sleeping_function_called_from_invalid_context_at_kernel/nsproxy.c
Date: Tue, 29 Jul 2025 09:27:56 +0200	[thread overview]
Message-ID: <87wm7ro3r7.ffs@tglx> (raw)
In-Reply-To: <aIgUUhKWesDpM0BJ@xsang-OptiPlex-9020>

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.

Thanks,

        tglx

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-07-29  7:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23  8:46 [tip:locking/futex] [futex] 56180dd20c: BUG:sleeping_function_called_from_invalid_context_at_kernel/nsproxy.c kernel test robot
2025-07-23  8:46 ` [LTP] " kernel test robot
2025-07-23 17:22 ` Thomas Gleixner
2025-07-23 17:22   ` [LTP] " Thomas Gleixner
2025-07-25  9:10   ` Oliver Sang
2025-07-25  9:10     ` [LTP] " Oliver Sang
2025-07-25 15:45     ` Thomas Gleixner
2025-07-25 15:45       ` [LTP] " Thomas Gleixner
2025-07-29  0:22       ` Oliver Sang
2025-07-29  0:22         ` [LTP] " Oliver Sang
2025-07-29  7:27         ` Thomas Gleixner [this message]
2025-07-29  7:27           ` Thomas Gleixner
2025-07-31  1:40           ` Oliver Sang
2025-07-31  1:40             ` [LTP] " Oliver Sang
2025-07-31 12:34             ` Thomas Gleixner
2025-07-31 12:34               ` [LTP] " Thomas Gleixner
2025-07-31 14:03               ` Thomas Gleixner
2025-07-31 14:03                 ` [LTP] " Thomas Gleixner
2025-08-06  8:01                 ` Oliver Sang
2025-08-06  8:01                   ` [LTP] " Oliver Sang
2025-08-06  8:19                   ` Thomas Gleixner
2025-08-06  8:19                     ` [LTP] " Thomas Gleixner
2025-08-06  8:35                     ` Oliver Sang
2025-08-06  8:35                       ` [LTP] " Oliver Sang
2025-08-06 10:39                       ` Thomas Gleixner
2025-08-06 10:39                         ` [LTP] " Thomas Gleixner
2025-08-07  5:21                         ` Oliver Sang
2025-08-07  5:21                           ` [LTP] " Oliver Sang

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=87wm7ro3r7.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=ltp@lists.linux.it \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=peterz@infradead.org \
    --cc=x86@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.