All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Guenter Roeck <groeck@google.com>
Cc: kernelci@lists.linux.dev, linux-rt-devel@lists.linux.dev,
	stable-rt@vger.kernel.org, Daniel Wagner <wagi@monom.org>
Subject: Re: PREEMPT_RT testing on kernelci
Date: Tue, 11 Feb 2025 16:37:59 +0100	[thread overview]
Message-ID: <20250211153759.5sSPp1PI@linutronix.de> (raw)
In-Reply-To: <CABXOdTeLUi8mKkV38SegM_n8=Uyykd-X+n7RysjpgAZfxxb5BQ@mail.gmail.com>

On 2025-02-11 07:33:57 [-0800], Guenter Roeck wrote:
> Unrelated to KernelCI - how stable is PREEMPT_RT in practice ? Reason
> for asking is that I enabled it for x86_64 together with lock
> debugging and got an almost immediate "sleeping function called"
> backtrace.

If I would have seen it I would have acted. My guess is that this is
something not a lot of people observed.

> Thanks,
> Guenter

Sebastian

  reply	other threads:[~2025-02-11 15:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11  9:05 PREEMPT_RT testing on kernelci Sebastian Andrzej Siewior
2025-02-11 11:33 ` Gustavo Padovan
2025-02-11 15:20   ` Sebastian Andrzej Siewior
2025-02-11 15:50     ` Gustavo Padovan
2025-02-11 16:26       ` Mark Brown
2025-02-13  8:52       ` Sebastian Andrzej Siewior
2025-04-11 19:44         ` Sebastian Andrzej Siewior
2025-04-14 15:14           ` Gustavo Padovan
2025-04-17 10:04             ` Sebastian Andrzej Siewior
2025-04-17 13:10               ` Gustavo Padovan
2025-04-17 15:11                 ` Sebastian Andrzej Siewior
2025-04-18 15:05                   ` Gustavo Padovan
2025-02-11 15:33 ` Guenter Roeck
2025-02-11 15:37   ` Sebastian Andrzej Siewior [this message]
2025-02-11 15:49     ` Guenter Roeck
2025-02-12 17:17   ` Donald Zickus
2025-02-12 17:59     ` Guenter Roeck

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=20250211153759.5sSPp1PI@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=groeck@google.com \
    --cc=kernelci@lists.linux.dev \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=stable-rt@vger.kernel.org \
    --cc=wagi@monom.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.