stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Sattler <sattler@med.uni-frankfurt.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: boot loop since 5.17.6
Date: Tue, 7 Jun 2022 16:17:26 +0200	[thread overview]
Message-ID: <4282db24-0c4e-df01-8b0e-06cf647a3351@med.uni-frankfurt.de> (raw)
In-Reply-To: <Yp88N2qL3HXLz0bi@kroah.com>

Hi Greg,

I did not yet start a bisect but looked at commits that modify
the same file again. And there was a promising one:

   22682a07acc3 objtool: Fix objtool regression on x32 systems

That one applies cleanly to both, 5.17.12 and 5.18.2, and also
fixes my boot-problem on both.

Thomas



Am 07.06.22 um 13:53 schrieb Greg KH:
> On Tue, Jun 07, 2022 at 01:40:03PM +0200, Thomas Sattler wrote:
>> Hi Thorsten,
>>
>> I just compiled 5.19-rc1 and my issue is solved there.
> 
> Any chance you can do 'git bisect' between 5.18 and 5.19-rc1 to find the
> commit that fixed the issue?
> 
> thanks,
> 
> greg k-h

  reply	other threads:[~2022-06-07 14:17 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 [this message]
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
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=4282db24-0c4e-df01-8b0e-06cf647a3351@med.uni-frankfurt.de \
    --to=sattler@med.uni-frankfurt.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=regressions@leemhuis.info \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).