From: Mike Galbraith <efault@gmx.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
John Ogness <john.ogness@linutronix.de>
Cc: RT <linux-rt-users@vger.kernel.org>
Subject: Re: v5.19-rc2-rt3: nouveau might sleep splat
Date: Sat, 25 Jun 2022 05:26:23 +0200 [thread overview]
Message-ID: <3a1359eb3d96454079e91011e99ff347b466f15b.camel@gmx.de> (raw)
In-Reply-To: <YrXMnCDoO2QPD9np@linutronix.de>
On Fri, 2022-06-24 at 16:39 +0200, Sebastian Andrzej Siewior wrote:
> On 2022-06-24 16:37:25 [+0206], John Ogness wrote:
> > On 2022-06-24, John Ogness <john.ogness@linutronix.de> wrote:
> > > As to this the actual problem reported in this thread, I believe
> > > this
> > > patch solves it:
> > >
> > > https://lore.kernel.org/lkml/20220609121709.12939-1-Jason@zx2c4.com
> >
> > There was a cleaner v2 later in the thread:
> >
> > https://lore.kernel.org/lkml/20220609123319.17576-1-Jason@zx2c4.com
>
> In that case v5.19-rc3-rt5 should no longer show it but I am still
> confused why we need to disable interrupts within vsnprintf().
It says they're disabled to simplify recursion tracking. I was
thinking maybe replace that with a local lock, but then the below
happened, rendering that little wart kinda moot for the moment.
07a22b61946f Revert "printk: add functions to prefer direct printing"
5831788afb17 Revert "printk: add kthread console printers"
2d9ef940f89e Revert "printk: extend console_lock for per-console locking"
007eeab7e9f0 Revert "printk: remove @console_locked"
05c96b3713aa Revert "printk: Block console kthreads when direct printing will be required"
20fb0c8272bb Revert "printk: Wait for the global console lock when the system is going down"
-Mike
next prev parent reply other threads:[~2022-06-25 3:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 9:25 v5.19-rc2-rt3: nouveau might sleep splat Mike Galbraith
2022-06-24 8:42 ` Sebastian Andrzej Siewior
2022-06-24 9:52 ` Mike Galbraith
2022-06-24 10:18 ` Sebastian Andrzej Siewior
2022-06-24 10:19 ` Sebastian Andrzej Siewior
2022-06-24 14:30 ` John Ogness
2022-06-24 14:31 ` John Ogness
2022-06-24 14:39 ` Sebastian Andrzej Siewior
2022-06-25 3:26 ` Mike Galbraith [this message]
2022-07-21 13:06 ` Mike Galbraith
2022-07-25 8:15 ` Sebastian Andrzej Siewior
2022-07-25 9:58 ` John Ogness
2022-07-25 13:26 ` Mike Galbraith
2022-08-03 16:10 ` Petr Mladek
2022-08-05 14:23 ` John Ogness
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=3a1359eb3d96454079e91011e99ff347b466f15b.camel@gmx.de \
--to=efault@gmx.de \
--cc=bigeasy@linutronix.de \
--cc=john.ogness@linutronix.de \
--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 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.