All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Sattler <sattler@med.uni-frankfurt.de>
To: Nathan Chancellor <nathan@kernel.org>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: boot loop since 5.17.6
Date: Fri, 3 Jun 2022 00:44:22 +0200	[thread overview]
Message-ID: <1f8a4bec-53bd-aaaa-49a7-b5ed4fc5ae34@med.uni-frankfurt.de> (raw)
In-Reply-To: <YpksflOG2Y1Xng89@dev-arch.thelio-3990X>

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"), 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.

Thomas


  reply	other threads:[~2022-06-02 22:44 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 [this message]
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
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=1f8a4bec-53bd-aaaa-49a7-b5ed4fc5ae34@med.uni-frankfurt.de \
    --to=sattler@med.uni-frankfurt.de \
    --cc=nathan@kernel.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.