From: Tony Lindgren <tony@atomide.com>
To: Marc Haber <mh+linux-kernel@zugschlus.de>
Cc: Sean Christopherson <seanjc@google.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
linux-kernel@vger.kernel.org,
Linux Regressions <regressions@lists.linux.dev>,
Linux KVM <kvm@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: Linux 6.5 speed regression, boot VERY slow with anything systemd related
Date: Wed, 6 Sep 2023 18:26:16 +0300 [thread overview]
Message-ID: <20230906152616.GE11676@atomide.com> (raw)
In-Reply-To: <ZPiPkSY6NRzfWV5Z@torres.zugschlus.de>
* Marc Haber <mh+linux-kernel@zugschlus.de> [230906 14:41]:
> With my tools I have found out that it really seems to be related to the
> CPU of the host. I have changed my VM definition to "copy host CPU
> configuration to VM" in libvirt and have moved this very VM (image and
> settings) to hosts with a "Ryzen 5 Pro 4650G" and to an "Intel Xeon
> E3-1246" where they work flawlessly, while on both APUs I have available
> ("AMD G-T40E" and "AMD GX-412TC SOC") the regression in 6.5 shows. And
> if I boot other VMs on the APUs with 6.5 the issue comes up. It is a
> clear regression since going back to 4.6's serial code solves the issue
> on the APUs.
Not sure why the CPU matters here..
One thing to check is if you have these in your .config:
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
Or do you maybe have CONFIG_SERIAL_CORE=m as loadable module?
If you have CONFIG_SERIAL_CORE=m, maybe you need to modprobe serial_base
if you have some minimal rootfs that does not automatically do it for you.
Regards,
Tony
next prev parent reply other threads:[~2023-09-06 15:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 6:35 Linux 6.5 speed regression, boot VERY slow with anything systemd related Marc Haber
2023-08-29 8:17 ` Bagas Sanjaya
2023-08-29 13:00 ` Marc Haber
2023-08-29 14:53 ` Sean Christopherson
2023-08-29 15:04 ` Marc Haber
2023-08-29 15:42 ` Sean Christopherson
2023-08-29 16:09 ` Marc Haber
2023-08-29 17:14 ` Sean Christopherson
2023-08-29 20:00 ` Marc Haber
2023-08-31 22:07 ` Sean Christopherson
2023-09-01 12:24 ` Tony Lindgren
2023-09-06 14:41 ` Marc Haber
2023-09-06 15:21 ` Tony Lindgren
2023-09-07 10:14 ` Marc Haber
2023-09-07 10:51 ` Tony Lindgren
2023-09-08 4:41 ` Tony Lindgren
2023-09-09 20:08 ` Marc Haber
2023-09-11 12:53 ` Tony Lindgren
2023-09-12 6:53 ` Marc Haber
2023-09-06 15:26 ` Tony Lindgren [this message]
2023-09-06 20:18 ` Marc Haber
2023-08-30 6:44 ` Marc Haber
2023-08-29 15:24 ` Marc Haber
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=20230906152616.GE11676@atomide.com \
--to=tony@atomide.com \
--cc=bagasdotme@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mh+linux-kernel@zugschlus.de \
--cc=pbonzini@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=seanjc@google.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