mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: Aaron Thompson <dev@aaront.org>, linux-kernel@vger.kernel.org
Subject: Re: printk.time causes rare kernel boot hangs
Date: Wed, 14 Jun 2023 16:53:48 +0200	[thread overview]
Message-ID: <20230614145348.GB1640563@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230614130945.GK1639749@hirez.programming.kicks-ass.net>

On Wed, Jun 14, 2023 at 03:09:45PM +0200, Peter Zijlstra wrote:
> On Wed, Jun 14, 2023 at 02:03:48PM +0100, Richard W.M. Jones wrote:
> > On Wed, Jun 14, 2023 at 02:53:20PM +0200, Peter Zijlstra wrote:
> > > Ooooh, what qemu version do you have? There were some really dodgy
> > > reports all around self modifying code, all reported on 7.2, that seems
> > > to have gone away with 8.
> > 
> > > Now, all of them were using TCG, and I think you're using KVM.
> > 
> > I'm using qemu-system-x86-8.0.0-4.fc39.x86_64 with KVM.  The host
> > kernel is 6.4.0-0.rc5.41.fc39.x86_64.
> > 
> > > I've at least 36000 cycles and still nothing :-(, let me go try your
> > > .config.
> > 
> > I can definitely reproduce this with your config (but AMD host), so
> > that's odd.  Let me try with Intel hardware and your config.  You
> > really should see this with only a few thousands iterations.
> 
> Yeah, I'm running on some ancient ivb-ep, let me try on the alderlake. I
> don't really have AMD machines at hand :-/

Using v6.4-rc6-37-gb6dad5178cea, and 36000+ cycles on the ADL (affine to
big cores) later and nothing :-(

Clearly I'm doing something wrong.

  reply	other threads:[~2023-06-14 14:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 13:41 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 [this message]
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
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=20230614145348.GB1640563@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=dev@aaront.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®