From: Mike Galbraith <efault@gmx.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-block <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>, RT <linux-rt-users@vger.kernel.org>
Subject: Re: block: lockdep splat with RT config v6.15+
Date: Fri, 11 Jul 2025 11:03:06 +0200 [thread overview]
Message-ID: <2fdd01857b95b086bcded0a006993e820d3efab0.camel@gmx.de> (raw)
In-Reply-To: <20250711085906._cTpNNFu@linutronix.de>
On Fri, 2025-07-11 at 10:59 +0200, Sebastian Andrzej Siewior wrote:
> On 2025-07-11 10:05:18 [+0200], Mike Galbraith wrote:
> > (was PREEMPT_RT vs i915)
> >
> > Ok, the splat below is not new to the 6.16 cycle, seems it landed in
> > the 6.15 cycle, as that also gripes but 6.14 boots clean.
>
> I don't remember how you triggered this. Do you happen to know if this
> is RT only or also triggers without the RT bits?
It's CONFIG_PREEMPT_RT dependent. The trigger is just boot for both my
lappy or desktop box.
-Mike
next prev parent reply other threads:[~2025-07-11 9:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 19:35 PREEMPT_RT vs i915 Ben Hutchings
2025-07-09 17:30 ` Ville Syrjälä
2025-07-09 19:44 ` Sebastian Andrzej Siewior
2025-07-09 20:09 ` Ville Syrjälä
2025-07-09 22:04 ` Matthew Brost
2025-07-10 6:30 ` Sebastian Andrzej Siewior
2025-07-10 15:21 ` Ville Syrjälä
2025-07-10 18:04 ` Matthew Brost
2025-07-10 18:15 ` Ville Syrjälä
2025-07-10 4:52 ` Mike Galbraith
2025-07-10 15:50 ` Ville Syrjälä
2025-07-11 2:36 ` Mike Galbraith
2025-07-11 3:33 ` Mike Galbraith
2025-07-11 8:05 ` block: lockdep splat with RT config v6.15+ Mike Galbraith
2025-07-11 8:59 ` Sebastian Andrzej Siewior
2025-07-11 9:03 ` Mike Galbraith [this message]
2025-07-10 6:41 ` PREEMPT_RT vs i915 Sebastian Andrzej Siewior
2025-07-10 15:04 ` Ville Syrjälä
2025-07-10 15:20 ` Sebastian Andrzej Siewior
2025-07-11 12:35 ` Maarten Lankhorst
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=2fdd01857b95b086bcded0a006993e820d3efab0.camel@gmx.de \
--to=efault@gmx.de \
--cc=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-rt-users@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox