From: "Richard W.M. Jones" <rjones@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
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:07:17 +0100 [thread overview]
Message-ID: <20230614150717.GG7636@redhat.com> (raw)
In-Reply-To: <20230614145348.GB1640563@hirez.programming.kicks-ass.net>
On Wed, Jun 14, 2023 at 04:53:48PM +0200, Peter Zijlstra wrote:
> 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 :-(
So I have just this minute reproduced it on Intel, after around ~2000
iterations.
On this machine I am using:
Host kernel: 6.3.7-200.fc38.x86_64
Guest kernel: git commit fb054096aea0576f0c0a61c598e5e9676443ee86
Guest config: defconfig + kvm_guest.config + CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT=y
QEMU: qemu-system-x86-8.0.0-4.fc39.x86_64 (using kvm_intel)
Hardware: Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz
> Clearly I'm doing something wrong.
I'm suspecting version of qemu may have something to do with it, but
honestly I don't know. Which qemu are you using?
I'll now try with upstream qemu from git in case there's something
about the Fedora qemu.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
next prev parent reply other threads:[~2023-06-14 15:08 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 [this message]
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=20230614150717.GG7636@redhat.com \
--to=rjones@redhat.com \
--cc=dev@aaront.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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.