All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Marcus Seyfarth <m.seyfarth@gmail.com>
Cc: Peter Huewe <peterhuewe@gmx.de>,
	Jarkko Sakkinen <jarkko@kernel.org>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Russ Weight <russell.h.weight@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Integrity <linux-integrity@vger.kernel.org>
Subject: Re: Slow boot and shutdown/reboot problems with 6.5.0+
Date: Mon, 11 Sep 2023 16:13:48 +0200	[thread overview]
Message-ID: <cb775a52-f28b-43d3-8af5-9b2547e13316@leemhuis.info> (raw)
In-Reply-To: <9a8d2090-a58e-49a0-3b1d-00bb5b8f04f2@gmail.com>

On 11.09.23 16:00, Bagas Sanjaya wrote:
> On 07/09/2023 20:56, Marcus Seyfarth wrote:
>> As to bisecting: Unfortunately I cannot afford the time right now to bisect this further as the system is used in production and already did invest a lot of time without success into it. Hopefully someone else can find the root cause of the problem. My systemd version is: 254.1, and I also use dbus 1.14.10 and dbus-broker 33.r35.g2220a84 which was configured with -D linux-4-17=true.
>>
> 
> [also Cc: Thorsten]
> 
> To Thorsten: It looks like the reporter can neither bisect nor
> test the mainline since he only has production machine instead.
> What can I (and the reporter do) in this case?

Well, unless someone[1] can find the root cause (either by guessing,
looking at the code-flow, the kernel warning, bisection, and others
things like that) we are out of luck; the only thing left is then to
hope that someone else will run into this and find the cause or that it
is accidentally fixed. That's definitely not ideal, but that's how it is
sometimes.

Ciao, Thorsten

[1] either the reporter or someone that sees this conversation or the
ticket; but things are quite confusing from the outside perspective and
a lot of private conversation seem to happen, so I doubt anyone will
take a closer look; a bisection is likely the best way forward here

      reply	other threads:[~2023-09-11 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 13:25 Fwd: Slow boot and shutdown/reboot problems with 6.5.0+ Bagas Sanjaya
     [not found] ` <CA+FbhJO8b5V_So2mMPu1ApKXTxk0ieWvNMa=HBTYTWDXLEA-ew@mail.gmail.com>
2023-09-08  1:38   ` Bagas Sanjaya
2023-09-11 14:00   ` Bagas Sanjaya
2023-09-11 14:13     ` Thorsten Leemhuis [this message]

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=cb775a52-f28b-43d3-8af5-9b2547e13316@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=bagasdotme@gmail.com \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.seyfarth@gmail.com \
    --cc=mcgrof@kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=regressions@lists.linux.dev \
    --cc=russell.h.weight@intel.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 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.