From: Pavin Joseph <me@pavinjoseph.com>
To: Thorsten Leemhuis <linux@leemhuis.info>,
Linux regressions mailing list <regressions@lists.linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: Re: guide on bisecting (was Re: [REGRESSION] kexec does firmware reboot in kernel v6.7.6)
Date: Mon, 4 Mar 2024 23:33:13 +0530 [thread overview]
Message-ID: <5a4e412e-e797-4db6-908e-09cb1e5f5623@pavinjoseph.com> (raw)
In-Reply-To: <e1d87d5c-97ee-4e08-84c9-61a02c81ca63@leemhuis.info>
On 3/4/24 11:46, Thorsten Leemhuis wrote:
> I'm not really familiar with openSUSE, but it set up a TW container and
> found that a package kernel-install-tools provides installkernel script.
> Not sure how good it works though. Could you maybe test that?
Yep, that package got me "installkernel" and it does all the
installation as expected. I only needed to change the symlink of
"/boot/<initrd|vmlinuz>" to point to the new ones created by it.
> kernel-install is normally meant to copy the image over to /boot/ as
> well afaik; maybe it did not do that in your case because you already
> had placed it there manually?
kernel-install doesn't do that in my testing, it also doesn't remove
anything AFAICT. 🧐
Kind regards,
Pavin Joseph.
next prev parent reply other threads:[~2024-03-04 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3a1b9909-45ac-4f97-ad68-d16ef1ce99db@pavinjoseph.com>
[not found] ` <7ebb1c90-544d-4540-87c0-b18dea963004@leemhuis.info>
[not found] ` <3a8453e8-03a3-462f-81a2-e9366466b990@pavinjoseph.com>
[not found] ` <a84c1a5d-3a8a-4eea-9f66-0402c983ccbb@leemhuis.info>
[not found] ` <806629e6-c228-4046-828a-68d397eb8dbc@pavinjoseph.com>
2024-03-03 8:36 ` Thorsten Leemhuis
2024-03-03 10:17 ` Pavin Joseph
2024-03-04 6:16 ` Thorsten Leemhuis
2024-03-04 18:03 ` Pavin Joseph [this message]
2024-03-05 6:12 ` Thorsten Leemhuis
2024-03-04 16:56 ` Takashi Iwai
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=5a4e412e-e797-4db6-908e-09cb1e5f5623@pavinjoseph.com \
--to=me@pavinjoseph.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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
all inboxes | Powered by JetHome®