stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Thomas Sattler <sattler@med.uni-frankfurt.de>,
	Nathan Chancellor <nathan@kernel.org>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: boot loop since 5.17.6
Date: Tue, 7 Jun 2022 11:52:22 +0200	[thread overview]
Message-ID: <a9a68c68-8830-2aa0-acbe-d5d3bb04968f@leemhuis.info> (raw)
In-Reply-To: <1f8a4bec-53bd-aaaa-49a7-b5ed4fc5ae34@med.uni-frankfurt.de>

Hi, this is your Linux kernel regression tracker. Sorry, I'm behind mail.

On 03.06.22 00:44, Thomas Sattler wrote:
> Am 02.06.22 um 23:32 schrieb Nathan Chancellor:
>>> Am 02.06.22 um 18:42 schrieb Thomas Sattler:
>>>>
>>>> I tried to compile 5.17.6 without the three mentioned diffs which
>>>> modify the following files:
>>>>
>>>>      tools/objtool/check.c   and
>>>>      tools/objtool/elf.c      and
>>>>      tools/objtool/include/objtool/elf.h
>>>>
>>>> and was then able to successfully boot 5.17.6.
>>
>> 5.17.6 has commit 60d2b0b1018a ("objtool: Fix code relocs vs weak
>> symbols"),

FWIW, that is 4abff6d48dbc in mainline

>> which has a known issue that is fixed with commit
>> ead165fa1042 ("objtool: Fix symbol creation"). If you apply ead165fa1042
>> on 5.17.6 or newer, does that resolve your issue?
> 
> I applied ead165fa1042 ontop of 5.17.12, but that did not make
> my system boot that kernel.

Was there any progress to get down to this? Peter, who authored
4abff6d48dbc, is not even CCed yet to this thread yet afaics.

BTW, 5.17 will likely be EOL in a week or two. Thomas, maybe it might be
the best to give 5.19-rc1 a shot and in case the regression is still
there start a new thread about this that focuses on the regression in
mainline. That makes things less confusing and the regression needs to
be fixed in mainline first anyway before it can be fixed in the stable
trees.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.

  reply	other threads:[~2022-06-07  9:53 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 [this message]
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
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=a9a68c68-8830-2aa0-acbe-d5d3bb04968f@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=nathan@kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=sattler@med.uni-frankfurt.de \
    --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).