From: John Ogness <john.ogness@linutronix.de>
To: "Marek Behún" <kabel@kernel.org>,
"Petr Mladek" <pmladek@suse.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: Boot stall regression from "printk for 5.19" merge
Date: Mon, 20 Jun 2022 00:29:16 +0206 [thread overview]
Message-ID: <87r13kwawb.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20220619204949.50d9154d@thinkpad>
Hi Marek,
On 2022-06-19, Marek Behún <kabel@kernel.org> wrote:
> the series
> https://lore.kernel.org/linux-kernel/YouKQw72H7y9EJQK@alley/
> merged by commit 537e62c865dc ("Merge tag 'printk-for-5.19' of
> git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux")
>
> and in particular the commit 09c5ba0aa2fc ("printk: add kthread console
> printers")
>
> causes a regression on arm64 (Marvell CN9130-CRB board) where the
> system boot freezes in most cases (and is unusable until restarted by
> watchdog), or, in some cases boots, but the console output gets mangled
> for a while (the serial console spits garbage characters).
Could you provide your kernel config and a complete kernel boot log (at
least as much as you get)? I would like to investigate the serial
driver. What you are describing sounds more like a serial bug. The
kthread console series has already uncovered serial driver bugs in
multiple drivers.
Thanks for reporting this.
John Ogness
next prev parent reply other threads:[~2022-06-19 22:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 18:49 Boot stall regression from "printk for 5.19" merge Marek Behún
2022-06-19 22:23 ` John Ogness [this message]
2022-06-19 22:31 ` John Ogness
2022-06-20 10:02 ` Marek Behún
2022-06-20 9:29 ` Marek Behún
2022-06-20 11:44 ` Petr Mladek
2022-06-20 11:47 ` Petr Mladek
2022-06-20 12:04 ` Ilpo Järvinen
2022-06-20 13:48 ` Linus Torvalds
2022-06-20 14:24 ` Petr Mladek
2022-06-20 15:14 ` [PATCH] printk/console: Enable console kthreads only when there is no boot console left Petr Mladek
2022-06-20 15:16 ` Petr Mladek
2022-06-20 18:38 ` Marek Behún
2022-06-20 19:10 ` Linus Torvalds
2022-06-20 22:25 ` Petr Mladek
2022-06-20 22:51 ` John Ogness
2022-06-24 22:41 ` Steven Rostedt
2022-06-29 8:29 ` Petr Mladek
2022-06-20 5:23 ` Boot stall regression from "printk for 5.19" merge Sergey Senozhatsky
2022-06-20 10:02 ` Marek Behún
2022-06-20 10:13 ` Sergey Senozhatsky
2022-06-20 10:29 ` Marek Behún
2022-06-20 11:01 ` Andy Shevchenko
2022-06-20 10:38 ` Daniel Palmer
2022-06-21 9:39 ` Thorsten Leemhuis
2022-07-04 9:32 ` Boot stall regression from "printk for 5.19" merge #forregzbot Thorsten Leemhuis
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=87r13kwawb.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=kabel@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=torvalds@linux-foundation.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