From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailout.rz.uni-frankfurt.de (mailout.rz.uni-frankfurt.de [141.2.22.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 29E1E3D99 for ; Thu, 2 Jun 2022 23:29:29 +0000 (UTC) Received: from smtpauth2.cluster.uni-frankfurt.de ([10.1.1.238]) by mailout.rz.uni-frankfurt.de with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nwuFq-00028d-IN; Fri, 03 Jun 2022 01:29:26 +0200 Received: from p57bcf53e.dip0.t-ipconnect.de ([87.188.245.62] helo=[192.168.2.17]) by smtpauth2.cluster.uni-frankfurt.de with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1nwuFq-0006G5-Gp; Fri, 03 Jun 2022 01:29:26 +0200 Message-ID: <88b0eb42-41eb-af0e-285c-05f86a5c5fea@med.uni-frankfurt.de> Date: Fri, 3 Jun 2022 01:29:26 +0200 Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: boot loop since 5.17.6 Content-Language: en-US To: Greg KH Cc: stable@vger.kernel.org, regressions@lists.linux.dev References: <11495172-41dd-5c44-3ef6-8d3ff3ebd1b2@med.uni-frankfurt.de> From: Thomas Sattler In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Am 02.06.22 um 22:08 schrieb Greg KH: > On Thu, Jun 02, 2022 at 06:14:43PM +0200, Thomas Sattler wrote: >> After applying "patch-5.17.5-6.part198.patch" compilation is >> broken. Still after applying "patch-5.17.5-6.part199.patch". >> After applying "patch-5.17.5-6.part200.patch", compilation >> works again but the resulting kernel now fails to boot. > > I have no idea what those random patches are, please can you say what > the upstream commit is? I took what I reverted from patch-5.17.5-6.xz. In your tree it matches what Nathan mentioned (60d2b0b1018a) plus d17f64c29512. Now, knowing that they were two patchsets, I compiled 5.17.12 twice, once without 60d2b0b1018a and once without d17f64c29512. And it turns out it is 60d2b0b1018a which breaks my system. Thomas