All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Sattler <sattler@med.uni-frankfurt.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: boot loop since 5.17.6
Date: Fri, 3 Jun 2022 01:29:26 +0200	[thread overview]
Message-ID: <88b0eb42-41eb-af0e-285c-05f86a5c5fea@med.uni-frankfurt.de> (raw)
In-Reply-To: <YpkY0RLWki4PJ49y@kroah.com>

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

  reply	other threads:[~2022-06-02 23:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 16:14 boot loop since 5.17.6 Thomas Sattler
2022-06-02 16:42 ` Thomas Sattler
2022-06-02 19:24   ` Thomas Sattler
2022-06-02 21:32     ` Nathan Chancellor
2022-06-02 22:44       ` Thomas Sattler
2022-06-07  9:52         ` Thorsten Leemhuis
2022-06-07 11:40           ` Thomas Sattler
2022-06-07 11:53             ` Greg KH
2022-06-07 14:17               ` Thomas Sattler
2022-06-07 16:55                 ` Greg KH
2022-06-07 12:02             ` Thorsten Leemhuis
2022-06-02 20:08 ` Greg KH
2022-06-02 23:29   ` Thomas Sattler [this message]
2022-06-03 12:57     ` Greg KH
2022-06-03 13:46       ` Thomas Sattler
2022-06-03 14:27         ` Greg KH

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=88b0eb42-41eb-af0e-285c-05f86a5c5fea@med.uni-frankfurt.de \
    --to=sattler@med.uni-frankfurt.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /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.