All of lore.kernel.org
 help / color / mirror / Atom feed
From: bhe <bhe@redhat.com>
To: kexec@lists.infradead.org
Subject: [ANNOUNCE] kexec-tools v2.0.24 preparation
Date: Tue, 29 Mar 2022 18:16:43 +0800	[thread overview]
Message-ID: <YkLci3fU3PYmRNig@MiWiFi-R3L-srv> (raw)
In-Reply-To: <YkLOjWtzcbhp2CZE@vergenet.net>

On 03/29/22 at 11:17am, Simon Horman wrote:
> On Sat, Mar 26, 2022 at 02:55:43PM +0800, RuiRui Yang wrote:
> > Hi Simon,
> > 
> > Recently RH CKI detected a kexec/kdump failure with kexec_load being
> > used,  the 2nd kernel can not boot, just reset to bios/firmware
> > instead.
> > 
> > This only happens with gcc 12.x compiled kexec-tools,  add
> > "-fno-tree-vectorize" to purgatory/Makefile CFLAGS make the bug
> > dissappear, but I hope people can help to verify and confirm it does
> > fix the problem.   It would be better to wait a few days so that we
> > can fix it in the coming release, what do you think?
> > 
> > Cced Baoquan who is handling the issue..
> > 
> > Thanks!
> 
> Hi RuiRui,
> 
> thanks for letting us know.
> 
> I'm happy with delaying the release for a short time to accommodate
> resolving this problem. Please let us know when there is some progress.

Thanks for quick response, Simon. I have sent a patch to fix this,
please check the patch v2 with subject 'purgatory: do not enable
vectorization automatically for purgatory compiling'.

I tested on machine where the issue can stably reproduced, and can
confirm adding -fno-tree-vectorize to compiling options of purgatory can
fix the issue.

Dave, please check if it is expected from you.



  reply	other threads:[~2022-03-29 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 15:01 [ANNOUNCE] kexec-tools v2.0.24 preparation Simon Horman
2022-03-26  6:55 ` RuiRui Yang
2022-03-29  9:17   ` Simon Horman
2022-03-29 10:16     ` bhe [this message]
2022-03-30  3:07       ` Dave Young
2022-03-30  8:35         ` Simon Horman

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=YkLci3fU3PYmRNig@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=kexec@lists.infradead.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.