From: boogs via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 75205@debbugs.gnu.org
Subject: bug#75205: guix package test failure on i686-linux (kexec-load-file test)
Date: Sun, 05 Jan 2025 11:31:02 -0500 [thread overview]
Message-ID: <87pll1kyt5.fsf@venatores.group> (raw)
In-Reply-To: <781419f2-6304-4c18-b01c-412121126ee5@posteo.net>
Forwarding my reply from this other relevant thread[1]:
> Hi,
> It looks like some people[1,2] including myself are running into an issue where the `guix system reconfigure` command fails, presumably because `KEXEC_FILE_DEBUG` is not supported in older kernel configurations.
>
> The output of reconfiguring my system is the same as Simen's[2] ending in:
>
> ```
> To complete the upgrade, run 'herd restart SERVICE' to stop,
> upgrade, and restart each service that was not automatically restarted.
> Run 'herd status' to view the list of services on your system.
> WARNING: (guile-user): imported module (guix build utils) overrides core binding `delete'
> guix system: error: kexec-load-file: Invalid argument
> ```
>
> My system runs a custom kernel configuration that I created via `make menuconfig` in the kernel repo. I suspect the issue lies here:
>
> ```
> (define (kexec-loading-program os)
> "Return a program that calls 'kexec_file_load' to allow rebooting into OS
> via 'kexec'."
> (let ((root-device (file-system-device
> (operating-system-root-file-system os))))
> (program-file
> "kexec-load-system.scm"
> (with-imported-modules '((guix build syscalls))
> #~(begin
> (use-modules (guix build syscalls))
> (let ((kernel (open-fdes #$(operating-system-kernel-file os)
> O_RDONLY))
> (initrd (open-fdes #$(operating-system-initrd-file os)
> O_RDONLY)))
> (kexec-load-file kernel initrd
> (string-join
> (list #$@(operating-system-kernel-arguments
> os root-device)))
> KEXEC_FILE_DEBUG)))))))
> ```
>
> This is the relevant snippet from my kernel configuration:
>
> ```
> #
> # Kexec and crash features
> #
> CONFIG_CRASH_CORE=y
> CONFIG_KEXEC_CORE=y
> CONFIG_KEXEC=y
> CONFIG_KEXEC_FILE=y
> CONFIG_KEXEC_JUMP=y
> CONFIG_CRASH_DUMP=y
> CONFIG_CRASH_HOTPLUG=y
> CONFIG_CRASH_MAX_MEMORY_RANGES=8192
> # end of Kexec and crash features
> # end of General setup
> ```
>
> [1] https://issues.guix.gnu.org/75320
> [2] https://issues.guix.gnu.org/75211
[1] https://issues.guix.gnu.org/75027
--
Boogs
prev parent reply other threads:[~2025-01-06 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 16:55 bug#75205: guix package test failure on i686-linux (kexec-load-file test) Dariqq
2025-01-01 4:17 ` Ian Eure
2025-01-04 18:11 ` Ludovic Courtès
2025-01-06 13:20 ` Ludovic Courtès
2025-01-05 16:31 ` boogs via Bug reports for GNU Guix [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pll1kyt5.fsf@venatores.group \
--to=bug-guix@gnu.org \
--cc=75205@debbugs.gnu.org \
--cc=boogs@venatores.group \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).