All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Sattler <sattler@med.uni-frankfurt.de>
To: stable@vger.kernel.org
Cc: regressions@lists.linux.dev
Subject: Re: boot loop since 5.17.6
Date: Thu, 2 Jun 2022 21:24:18 +0200	[thread overview]
Message-ID: <181a6369-e373-b020-2059-33fb5161d8d3@med.uni-frankfurt.de> (raw)
In-Reply-To: <c3b370a8-193e-329b-c73a-1371bd62edf3@med.uni-frankfurt.de>

with these three diffs reverted, I was able to boot
all affected 5.17.x kernels (x={6,7,8,9,10,11,12})



Am 02.06.22 um 18:42 schrieb Thomas Sattler:
> some more information:
> 
> $ cat /proc/version
> Linux version 5.17.5 (root@dragon) (x86_64-pc-linux-gnu-gcc (Gentoo
> 11.2.1_p20220115 p4) 11.2.1 20220115, GNU ld (Gentoo 2.37_p1 p2) 2.37)
> #130 SMP PREEMPT Thu Apr 28 10:50:24 CEST 2022
> 
> $ uname -mi
> x86_64 GenuineIntel
> 
> 
> 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.

  reply	other threads:[~2022-06-02 19:24 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 [this message]
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
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=181a6369-e373-b020-2059-33fb5161d8d3@med.uni-frankfurt.de \
    --to=sattler@med.uni-frankfurt.de \
    --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.