unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: raingloom <raingloom@riseup.net>
To: phodina <phodina@protonmail.com>
Cc: phodina via <help-guix@gnu.org>
Subject: Re: Kernel panic on new machine
Date: Thu, 14 Apr 2022 15:57:36 +0200	[thread overview]
Message-ID: <20220414155736.2dff3399@riseup.net> (raw)
In-Reply-To: <jBhfNtHPJ2ApLnb_8N3ElqdMxMorhAQD5lMDZduzBjzmpmF-JIpFiO8CqKhV3LKR2PMKF0bqL8r6cS9u27qxUcJGcshMWGk_lBbXE-6MyJA=@protonmail.com>

On Thu, 14 Apr 2022 07:47:47 +0000
phodina <phodina@protonmail.com> wrote:

> Hi,
> 
> > This is a Guix init issue, not "really" a kernel panic. As you can
> > see, there is some kind of error in the Scheme code being run at
> > boot time, but instead of being dropped into a debug shell, it
> > exits, which causes the kernel to panic.
> > This is because Guile is running as PID 1, that is, it is the first
> > process the kernel starts. PID 1 is kinda special and AFAIK it is
> > not allowed to exit, ever. Otherwise you get that panic.  
> 
> yes, I know Guix init process exiting and due to being PID 1 kernel
> panics.
> 
> In the meantime I reinstalled Guix again and it booted correctly, no
> idea what caused it.
> 
> 
> However, my question was/still is how to fix this? Also is there a
> way to determine what caused this? Is there a way to launch the debug
> shell instead of exiting?
> 
> PS: Sorry for the image spam but it appeared that the image was not
> posted the first time so I tried also sending a smaller image
> 
> Petr
> 

Maybe you could boot that system profile in QEMU.
It looks like it is trying to open a debug shell but failing, so... not
sure what you could do in that case if you are on bare metal. At least
on QEMU you might be able to generate some kind of core dump or attach
gdb to it or something.


      reply	other threads:[~2022-04-14 14:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 16:16 Kernel panic on new machine phodina via
2022-04-11 16:51 ` phodina via
2022-04-11 17:03   ` phodina via
2022-04-11 23:26   ` phodina via
2022-04-14  1:14   ` raingloom
2022-04-14  7:47     ` phodina
2022-04-14 13:57       ` raingloom [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=20220414155736.2dff3399@riseup.net \
    --to=raingloom@riseup.net \
    --cc=help-guix@gnu.org \
    --cc=phodina@protonmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).