All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Ogness <john.ogness@linutronix.de>
To: Conor Dooley <conor.dooley@microchip.com>,
	Petr Mladek <pmladek@suse.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	Conor Dooley <conor@kernel.org>,
	senozhatsky@chromium.org, rostedt@goodmis.org,
	linux-kernel@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [resend][bug] low-probability console lockups since 5.19
Date: Thu, 29 Sep 2022 16:19:03 +0206	[thread overview]
Message-ID: <877d1m46c0.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <YzV40LbMHcW1S/9O@wendy>

On 2022-09-29, Conor Dooley <conor.dooley@microchip.com> wrote:
> I will, possibly tonight but probably not, run the bisection again
> with the threaded printer merge reverted. Hopefully it is not filled
> with conflicts if I go that way...

It might be easier for you to just apply the following patch to run your
tests . This simple patch disables kthread usage.

John Ogness


diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index b095fb5f5f61..9679887c0805 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -3605,6 +3605,10 @@ static int __init printk_activate_kthreads(void)
 {
 	struct console *con;
 
+	/* hack: never activate kthreads */
+	if (!printk_kthreads_available)
+		return 0;
+
 	console_lock();
 	printk_kthreads_available = true;
 	for_each_console(con)

  reply	other threads:[~2022-09-29 14:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 16:24 [resend][bug] low-probability console lockups since 5.19 Conor Dooley
2022-09-26 10:32 ` Petr Mladek
2022-09-26 13:07   ` Conor Dooley
2022-09-28 16:55 ` Conor Dooley
2022-09-29  9:06   ` Thorsten Leemhuis
2022-09-29  9:29     ` Conor Dooley
2022-09-29 10:12       ` Petr Mladek
2022-09-29 10:52         ` Conor Dooley
2022-09-29 14:13           ` John Ogness [this message]
2022-09-29 21:22             ` Conor Dooley

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=877d1m46c0.fsf@jogness.linutronix.de \
    --to=john.ogness@linutronix.de \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.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.