Regressions List Tracking
 help / color / mirror / Atom feed
From: Pavin Joseph <me@pavinjoseph.com>
To: stable@vger.kernel.org
Cc: regressions@lists.linux.dev
Subject: [REGRESSION] kexec does firmware reboot in kernel v6.7.6
Date: Fri, 1 Mar 2024 19:40:09 +0530	[thread overview]
Message-ID: <3a1b9909-45ac-4f97-ad68-d16ef1ce99db@pavinjoseph.com> (raw)

Hello everyone,

#regzbot introduced v6.7.5..v6.7.6

I'm experiencing an issue where kexec does a full firmware reboot 
instead of kexec reboot.

Issue first submitted at OpenSuse bugzilla [0].

OS details as follows:
Distributor ID:	openSUSE
Description:	openSUSE Tumbleweed-Slowroll
Release:	20240213

Issue has been reproduced by building kernel from source.

kexec works as expected in kernel v6.7.5.
kexec does full firmware reboot in kernel v6.7.6.

I followed the docs here [1] to perform git bisect and find the culprit, 
hope it's alright as I'm quite out of my depth here.

Git bisect logs:
git bisect start
# status: waiting for both good and bad commits
# bad: [b631f5b445dc3379f67ff63a2e4c58f22d4975dc] Linux 6.7.6
git bisect bad b631f5b445dc3379f67ff63a2e4c58f22d4975dc
# status: waiting for good commit(s), bad commit known
# good: [004dcea13dc10acaf1486d9939be4c793834c13c] Linux 6.7.5
git bisect good 004dcea13dc10acaf1486d9939be4c793834c13c

Let me know if there's anything else I can do to help troubleshoot the 
issue.

[0]: https://bugzilla.suse.com/show_bug.cgi?id=1220541
[1]: https://docs.kernel.org/admin-guide/bug-bisect.html

Kind regards,
Pavin Joseph.

             reply	other threads:[~2024-03-01 14:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 14:10 Pavin Joseph [this message]
2024-03-01 14:45 ` [REGRESSION] kexec does firmware reboot in kernel v6.7.6 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
2024-03-03  8:36         ` guide on bisecting (was Re: [REGRESSION] kexec does firmware reboot in kernel v6.7.6) Thorsten Leemhuis
2024-03-03 10:17           ` Pavin Joseph
2024-03-04  6:16             ` Thorsten Leemhuis
2024-03-04 18:03               ` Pavin Joseph
2024-03-05  6:12                 ` Thorsten Leemhuis
2024-03-04 16:56             ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
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
2024-03-12 20:09         ` Steve Wahl
2024-03-12 22:02         ` Steve Wahl
2024-03-13 12:16           ` Eric W. Biederman
2024-03-13 16:17             ` Steve Wahl
2024-03-14  9:25               ` Dave Young

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=3a1b9909-45ac-4f97-ad68-d16ef1ce99db@pavinjoseph.com \
    --to=me@pavinjoseph.com \
    --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 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 read-only IMAP folder(s) and NNTP newsgroup(s).