All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavin Joseph <me@pavinjoseph.com>
To: Steve Wahl <steve.wahl@hpe.com>, Eric Hagberg <ehagberg@gmail.com>
Cc: dave.hansen@linux.intel.com, regressions@lists.linux.dev,
	stable@vger.kernel.org
Subject: Re: [REGRESSION] kexec does firmware reboot in kernel v6.7.6
Date: Wed, 13 Mar 2024 00:12:31 +0530	[thread overview]
Message-ID: <42e3e931-2883-4faf-8a15-2d7660120381@pavinjoseph.com> (raw)
In-Reply-To: <ZfBxIykq3LwPq34M@swahl-home.5wahls.com>

On 3/12/24 20:43, Steve Wahl wrote:
> But I don't want to introduce a new command line parameter if the
> actual problem can be understood and fixed.  The question is how much
> time do I have to persue a direct fix before some other action needs
> to be taken?

Perhaps the kexec maintainers [0] can be made aware of this and you 
could coordinate with them on a potential fix?

Currently maintained by
P:      Simon Horman
M:      horms@verge.net.au
L:      kexec@lists.infradead.org

I hope the root cause can be fixed instead of patching it over with a 
flag to suppress the problem, but I don't know how regressions are 
handled here.

[0]: 
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/tree/AUTHORS

Pavin.

  reply	other threads:[~2024-03-12 18:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 10:39 [REGRESSION] kexec does firmware reboot in kernel v6.7.6 Eric Hagberg
2024-03-07 16:33 ` Steve Wahl
     [not found]   ` <CAJbxNHfPHpbzRwfuFw6j7SxR1OsgBH2VJFPnchBHTtRueJna4A@mail.gmail.com>
2024-03-12 15:13     ` Steve Wahl
2024-03-12 18:42       ` Pavin Joseph [this message]
2024-03-12 20:09         ` Steve Wahl
2024-03-12 22:02         ` Steve Wahl
2024-03-12 22:02           ` Steve Wahl
2024-03-13 12:16           ` Eric W. Biederman
2024-03-13 12:16             ` Eric W. Biederman
2024-03-13 16:17             ` Steve Wahl
2024-03-13 16:17               ` Steve Wahl
2024-03-14  9:25               ` Dave Young
2024-03-14  9:25                 ` Dave Young
  -- strict thread matches above, loose matches on Subject: below --
2024-03-01 14:10 Pavin Joseph
2024-03-01 14:45 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-02  8:24   ` Pavin Joseph
2024-03-02 15:17     ` Linux regression tracking (Thorsten Leemhuis)
2024-03-02 16:10       ` Pavin Joseph
2024-03-03  0:00         ` Steve Wahl
2024-03-03  6:32           ` Pavin Joseph
2024-03-04 16:15             ` Steve Wahl
2024-03-04 17:48               ` Pavin Joseph
2024-03-05 15:25                 ` Steve Wahl
2024-03-05 19:58                   ` Pavin Joseph
2024-03-06  3:09                     ` Pavin Joseph
2024-03-06 15:50                       ` Steve Wahl

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=42e3e931-2883-4faf-8a15-2d7660120381@pavinjoseph.com \
    --to=me@pavinjoseph.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=ehagberg@gmail.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=steve.wahl@hpe.com \
    /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.