linux-kernel - Re: Slow boot and shutdown/reboot problems with 6.5.0+

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <cb775a52-f28b-43d3-8af5-9b2547e13316@leemhuis.info>
Date:   Mon, 11 Sep 2023 16:13:48 +0200
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Bagas Sanjaya <bagasdotme@...il.com>,
        Marcus Seyfarth <m.seyfarth@...il.com>
Cc:     Peter Huewe <peterhuewe@....de>,
        Jarkko Sakkinen <jarkko@...nel.org>,
        Jason Gunthorpe <jgg@...pe.ca>,
        Luis Chamberlain <mcgrof@...nel.org>,
        Russ Weight <russell.h.weight@...el.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Regressions <regressions@...ts.linux.dev>,
        Linux Integrity <linux-integrity@...r.kernel.org>
Subject: Re: Slow boot and shutdown/reboot problems with 6.5.0+

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