From: Attila Lendvai <attila@lendvai.name>
To: Richard Sent <richard@freakingpenguin.com>
Cc: Nathan Dehnel <ncdehnel@gmail.com>,
raingloom <raingloom@riseup.net>,
guix-devel@gnu.org
Subject: Re: watchdog triggered auto-rollback
Date: Wed, 29 May 2024 20:41:44 +0000 [thread overview]
Message-ID: <dSd9q9kIFz2GMNR1fRb7EC_CBufHDox1E7pYja2EvpWcXPvmpPVaC12K-gmdegteZUOhm7bqz1-0baxIqqIaZJ0eTdHcv_vJWgkkAqAdgyI=@lendvai.name> (raw)
In-Reply-To: <79655E3E-D6D6-4425-AEEC-8B5AB3374321@freakingpenguin.com>
> > i'm afraid that's not the case currently:
> >
> > %guile-static-stripped crashes with a sigsegv (i.e. the guile used in the initrd (?))
> > https://issues.guix.gnu.org/71211
>
>
> Interesting. Is this a recent bug? When I was trying to bring up
> Guix on the VisionFive 2 I was being dropped into a Guile REPL when
> the initrd failed to find the root partition.
well, the reproducer "works" on a recent x86_64, but i originally noticed this long ago (maybe a year even). back then i investigated an early crash in the boot, and reached %GUILE-STATIC-STRIPPED, and made a TODO note to further investigate. then i forgot most of what happened, and recently i opened a bug report based on my note.
since then EXPRESSION->INITRD may have changed, because it now uses %GUILE-STATIC-INITRD. but it's created with the same MAKE-GUILE-STATIC-STRIPPED that produces the faulty %GUILE-STATIC-STRIPPED, so...
in short: the reproducer crashes both %GUILE-STATIC-STRIPPED and %GUILE-STATIC-INITRD on x86_64, and i believe that it crashes the same in the early phase of the boot when it tries to enter the debugger.
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
Freedom cannot be given… it can only be taken away.
next prev parent reply other threads:[~2024-05-29 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 0:52 watchdog triggered auto-rollback Nathan Dehnel
2024-05-28 1:46 ` Richard Sent
2024-05-28 10:10 ` Attila Lendvai
2024-05-29 13:45 ` Richard Sent
2024-05-29 20:41 ` Attila Lendvai [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-24 12:50 raingloom
2024-05-25 16:58 ` Richard Sent
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='dSd9q9kIFz2GMNR1fRb7EC_CBufHDox1E7pYja2EvpWcXPvmpPVaC12K-gmdegteZUOhm7bqz1-0baxIqqIaZJ0eTdHcv_vJWgkkAqAdgyI=@lendvai.name' \
--to=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=ncdehnel@gmail.com \
--cc=raingloom@riseup.net \
--cc=richard@freakingpenguin.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.