All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Bert Karwatzki <spasswolf@web.de>,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	bpf@vger.kernel.org, linux-rt-users@vger.kernel.org,
	linux-rt-devel@lists.linux.dev,
	Thomas Gleixner <tglx@linutronix.de>,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>
Subject: Re: BUG: scheduling while atomic with PREEMPT_RT=y and bpf selftests
Date: Thu, 5 Jun 2025 14:51:33 +0200	[thread overview]
Message-ID: <20250605125133.RSTingmi@linutronix.de> (raw)
In-Reply-To: <20250605084816.3e5d1af1@gandalf.local.home>

On 2025-06-05 08:48:38 [-0400], Steven Rostedt wrote:
> On Thu,  5 Jun 2025 11:19:03 +0200
> Bert Karwatzki <spasswolf@web.de> wrote:
> 
> > This patch seems to create so much output that the orginal error message and
> > backtrace often get lost, so I needed several runs to get a meaningful message
> > when running
> 
> Are you familiar with preempt count tracing?

I have an initial set of patches to tackle this problem, I'm going to
send them after the merge window.

Sebastian

  reply	other threads:[~2025-06-05 12:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05  9:19 BUG: scheduling while atomic with PREEMPT_RT=y and bpf selftests Bert Karwatzki
2025-06-05 12:48 ` Steven Rostedt
2025-06-05 12:51   ` Sebastian Andrzej Siewior [this message]
2025-06-08  8:45     ` Bert Karwatzki
2025-06-08 15:53       ` Bert Karwatzki
2025-06-09 11:37         ` Bert Karwatzki
2025-06-14 12:01           ` Bert Karwatzki
2025-06-15 22:12             ` Bert Karwatzki
2025-06-16  6:28               ` Sebastian Andrzej Siewior
2025-06-06 13:13   ` Bert Karwatzki
2025-06-06 13:57     ` Steven Rostedt
  -- strict thread matches above, loose matches on Subject: below --
2025-05-25 22:47 Bert Karwatzki
2025-05-26  1:32 ` Alexei Starovoitov
2025-05-26  9:22   ` Bert Karwatzki
2025-05-27  7:19   ` Sebastian Andrzej Siewior
2025-05-25 12:14 Bert Karwatzki
2025-05-25 11:54 Bert Karwatzki

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=20250605125133.RSTingmi@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=spasswolf@web.de \
    --cc=tglx@linutronix.de \
    /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.