From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Aaron Thompson <dev@aaront.org>,
linux-kernel@vger.kernel.org
Subject: Re: printk.time causes rare kernel boot hangs
Date: Thu, 15 Jun 2023 09:40:40 +0200 [thread overview]
Message-ID: <20230615074040d166068b@mail.local> (raw)
In-Reply-To: <20230614173430.GB10301@redhat.com>
Hello,
On 14/06/2023 18:34:30+0100, Richard W.M. Jones wrote:
>
> FWIW attached is a test program that runs the qemu instances in
> parallel (up to 8 threads), which seems to be a quicker way to hit the
> problem for me. Even on Intel, with this test I can hit the bug in a
> few hundred iteration.
>
I'm just chiming in to say that we do hit the same issue on the Yocto
Project CI. We are using qemu 8.0.0 on Intel hardware and a 6.1 kernel.
I see that f31dcb152a3d0816e2f1deab4e64572336da197d hasn't been
backported so it may not be the culprit. However, this seems to have
started happening when we switched from 5.15 to 6.1.
Regards,
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-06-15 7:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 13:41 printk.time causes rare kernel boot hangs Richard W.M. Jones
2023-06-13 14:07 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-06-18 10:25 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-06-14 9:21 ` Peter Zijlstra
2023-06-14 9:45 ` Richard W.M. Jones
2023-06-14 10:30 ` Richard W.M. Jones
2023-06-14 10:39 ` Richard W.M. Jones
2023-06-14 11:35 ` Peter Zijlstra
2023-06-14 11:43 ` Richard W.M. Jones
2023-06-14 12:37 ` Richard W.M. Jones
2023-06-14 12:53 ` Peter Zijlstra
2023-06-14 13:03 ` Richard W.M. Jones
2023-06-14 13:09 ` Peter Zijlstra
2023-06-14 14:53 ` Peter Zijlstra
2023-06-14 15:07 ` Richard W.M. Jones
2023-06-14 15:19 ` Peter Zijlstra
2023-06-14 15:22 ` Richard W.M. Jones
2023-06-14 15:31 ` Peter Zijlstra
2023-06-14 15:50 ` Richard W.M. Jones
2023-06-14 17:34 ` Richard W.M. Jones
2023-06-15 7:40 ` Alexandre Belloni [this message]
2023-06-15 7:48 ` Richard W.M. Jones
2023-06-14 11:20 ` Peter Zijlstra
2023-06-14 11:16 ` Peter Zijlstra
2023-06-14 11:22 ` Richard W.M. Jones
2023-06-14 11:26 ` Richard W.M. Jones
2023-06-15 11:04 ` YiFei Zhu
2023-06-15 11:29 ` Richard W.M. Jones
2023-06-15 11:31 ` Richard W.M. Jones
2023-06-15 12:20 ` Dr. David Alan Gilbert
2023-06-15 12:21 ` Richard W.M. Jones
2023-06-15 12:23 ` Richard W.M. Jones
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=20230615074040d166068b@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=dev@aaront.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rjones@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).