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: Mon, 11 Sep 2023 15:53:40 +0300 [thread overview]
Message-ID: <20230911125340.GB5285@atomide.com> (raw)
In-Reply-To: <ZPzQvXUW+dbkLMZ2@torres.zugschlus.de>
* Marc Haber <mh+linux-kernel@zugschlus.de> [230909 20:08]:
> On Thu, Sep 07, 2023 at 01:51:50PM +0300, Tony Lindgren wrote:
> > Still a minimal reproducable test case is needed.. Or do you have the
> > dmesg output of the failing boot?
>
> I have both dmesg output of a failing boot (with my kernel) and of a
> successful boot (with the Debian kernel). Attached.
Thanks I don't see anything strange there, serial ports are probed in
both cases.
> In the last few days I have made some additional experiments. Since 6.5
> has landed in Debian experimental in the mean time, I tried with the
> Debian kernel: It works. I then used the Debian .config with my kernel
> tree and my build environment, it works as well. I tried again with my
> own .config, doesn't work.
OK
> I spent the next days with kind of binary searching the .config
> differences between mine and Debian's (they're huge), and I now have two
> configurations that only differ in CONFIG_PREEMPT_VOLUNTARY and
> CONFIG_PREMPT. The version with CONFIG_PREEMPT_VOLUNTARY seems to work
> (both attached). Sadly, my "own" .config uses CONFIG_PREEMPT_VOLUNTARY
> and doesn't work, so the actual problem seems to be a bit more complex
> still.
OK
Regards,
Tony
next prev parent reply other threads:[~2023-09-11 22:11 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 [this message]
2023-09-12 6:53 ` Marc Haber
2023-09-06 15:26 ` Tony Lindgren
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=20230911125340.GB5285@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