From: "Marek Behún" <kabel@kernel.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: John Ogness <john.ogness@linutronix.de>,
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 12:02:34 +0200 [thread overview]
Message-ID: <20220620120234.5a65ac97@thinkpad> (raw)
In-Reply-To: <YrAEUM20n3Rc4aOn@google.com>
On Mon, 20 Jun 2022 14:23:28 +0900
Sergey Senozhatsky <senozhatsky@chromium.org> wrote:
> On (22/06/19 20:49), Marek Behún wrote:
> [..]
> > 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).
>
> Can you please try disabling console kthreads and see how the boot
> process goes? Just `return 0` from printk_activate_kthreads() (I think
> this should do the trick).
This indeed makes the problem go away...
>
> > The stall example:
> >
> > ...
> > [ 1.108141] io scheduler mq-deadline registered
> > [ 1.108143] io scheduler kyber registered
> > [ 1.163484] armada-ap806-pinctrl f06f4000.system-controller:pinctrl: registered pinctrl driver
> > [
> >
> > Or another:
> >
> > ...
> > [ 1.108155] io scheduler mq-deadline registered
> > [ 1.108156] io scheduler kyber registered
> > [ 1.162991] armada-ap806-pinctrl f06f4000.system-controller:pinctrl: registered pinctrl driver
> > [ 1.163361] armada-cp110-pinctrl f2440000.system-controller:pinctrl: registered pinctrl driver
> > [ 1.180827] mv_xor_v2 f0400000.xor: Marvell Version 2 XOR driver
> > [
> >
> > The garbage example:
> >
> > ...
> > [ 0.920951] raid6: using neon recovery algorithm
> > [ 0.921228] iommu: Default domain type: Translated
> > %
> >
> > gb@k+cFL/[ 4.954974] DSA: tree 0 setup
> > [ 4.955286] cfg80211: Loading compiled-in X.509 certificates for regulatory database
>
> This is pretty suspicious. I don't see how console kthreads would
> corrupt the output. I suspect that something else is going on, some
> memory corruption, etc.
Maybe multiple threads are writing to serial registers, or something...
Marek
next prev parent reply other threads:[~2022-06-20 10:03 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
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 [this message]
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=20220620120234.5a65ac97@thinkpad \
--to=kabel@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=senozhatsky@chromium.org \
--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