From: Pavin Joseph <me@pavinjoseph.com>
To: Steve Wahl <steve.wahl@hpe.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
Dave Hansen <dave.hansen@linux.intel.com>,
stable@vger.kernel.org
Subject: Re: [REGRESSION] kexec does firmware reboot in kernel v6.7.6
Date: Wed, 6 Mar 2024 01:28:28 +0530 [thread overview]
Message-ID: <294c28ba-25c2-4db4-9dea-616ed1e2ea30@pavinjoseph.com> (raw)
In-Reply-To: <Zec5Ubr7G9NbnIyq@swahl-home.5wahls.com>
On 3/5/24 20:55, Steve Wahl wrote:
> In the meantime, if you want to try
> figuring out how to increase the memory allocated for kexec kernel
> purposes, that might correct the problem.
I tried all the options and variations possible in kexec. Don't know how
useful this is but it seems there's a hard limit imposed by kexec on the
size of the kernel image, irrespective of the format.
pavin@suse-laptop:~> sudo /usr/sbin/kexec --debug --kexec-syscall-auto
--load '/usr/lib/modules/6.7.6-1-default/vmlinux'
--initrd='/boot/initrd-6.7.6-1-default'
--append='root=/dev/mapper/suse-system crashkernel=341M,high
crashkernel=72M,low security=apparmor mitigations=auto'
Try gzip decompression.
Invalid memory segment 0x1000000 - 0x2c60fff
pavin@suse-laptop:~> file /usr/lib/modules/6.7.6-1-default/vmlinux
/usr/lib/modules/6.7.6-1-default/vmlinux: ELF 64-bit LSB executable,
x86-64, version 1 (SYSV), statically linked,
BuildID[sha1]=cd9816be5099dbe04750b2583fe34462de6dcdca, not stripped
Kind regards,
Pavin Joseph.
next prev parent reply other threads:[~2024-03-05 19:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 14:10 [REGRESSION] kexec does firmware reboot in kernel v6.7.6 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 [this message]
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
2024-10-22 18:51 ` David Woodhouse
2024-10-22 22:06 ` Steve Wahl
2024-10-23 7:39 ` David Woodhouse
2024-10-23 11:07 ` Kalra, Ashish
2024-10-23 11:39 ` David Woodhouse
2024-10-23 13:29 ` Kalra, Ashish
2024-10-23 13:50 ` David Woodhouse
2024-10-24 10:08 ` Kalra, Ashish
2024-10-23 15:32 ` 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=294c28ba-25c2-4db4-9dea-616ed1e2ea30@pavinjoseph.com \
--to=me@pavinjoseph.com \
--cc=dave.hansen@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox