Re: Kernel panic on new machine

[raingloom]

On Thu, 14 Apr 2022 07:47:47 +
phodina  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.

Re: Kernel panic on new machine

[phodina]

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

Re: Kernel panic on new machine

[raingloom]

On Mon, 11 Apr 2022 16:51:30 +
phodina via  wrote:

> Hi,
> 
> I've installed Guix to a new machine and after rebooting the live
> install I get kernel panic.
> 
> The machine is Dell x86_64 uefi machine with FAT32 boot partition and
> Luks partition with Btrfs filesystem with rootfs.
> 
> Could you please help me?
> 
> Petr

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.

Re: Kernel panic on new machine

[phodina via]

Hi,

I've installed Guix to a new machine and after rebooting the live install I get 
kernel panic.

The machine is Dell x86_64 uefi machine with FAT32 boot partition and Luks 
partition with Btrfs filesystem with rootfs.

Could you please help me?

Petr

Re: Kernel Panic

[Raghav Gururajan]

> Can you post a picture or transcript of the kernel panic?  Please also
> include your system configuration and some information about the
> hardware you are using (i.e. laptop model).

Sure, please find the information at 
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=37917.

> > I was wondering whether guix uses LTS releases of linux-libre or not?
> 
> The default kernel in Guix is the latest and greatest, but you can
> choose to use one of the LTS releases that are available (4.4, 4.9, 4.14
> or 4.19) by adjusting the 'kernel' field of your system configuration.

I see.

> > Or is there any other way to prevent these kernel panic?
> 
> Try pulling the power instead of shutting down...  :-P

I ended up doing that anyway 

Regards,
RG.



signature.asc
Description: This is a digitally signed message part

Re: Kernel Panic

[Marius Bakke]

Raghav Gururajan  writes:

> Whenever I shutdown my system, I end up with kernel panic, 50% of the
> time.

Can you post a picture or transcript of the kernel panic?  Please also
include your system configuration and some information about the
hardware you are using (i.e. laptop model).

> I was wondering whether guix uses LTS releases of linux-libre or not?

The default kernel in Guix is the latest and greatest, but you can
choose to use one of the LTS releases that are available (4.4, 4.9, 4.14
or 4.19) by adjusting the 'kernel' field of your system configuration.

> Or is there any other way to prevent these kernel panic?

Try pulling the power instead of shutting down...  :-P

(on a more serious note, it could be interesting to see if holding
AltGr+SysRq and typing 'reisub' also triggers this problem, and at which
letter).


signature.asc
Description: PGP signature

Kernel Panic

[Raghav Gururajan]

Hello Guix!

Whenever I shutdown my system, I end up with kernel panic, 50% of the
time.

I was wondering whether guix uses LTS releases of linux-libre or not?

Or is there any other way to prevent these kernel panic?

Thank you!

Regards,
RG.


signature.asc
Description: This is a digitally signed message part

Re: Kernel panic while building VM

[Enrico Schwass]

Hello


>>> Could you try again and report (1) what you did, (2) the
 ‘operating-system’ configuration you used, and (3) the error messages
>>> you see and when you see them?
>>> 
 I will test the hardware with Guix 12 at the weekend
>>> 
>>> Please stick to 0.13.0.  0.12.0 is relatively old, so you’ll find that
>>> many pre-built binaries are missing, not to mention many security fixes.
>> 
>> I use the lightweight-desktop.scm just changed user name and partition 
>> setup. Here are some screenshots
> 
> It’s hard to tell much here.  Is this happening with 0.13.0?  One of the
> screenshots shows that Python was being built from source, which is
> suspicious.

I used the --fallback option due to network problems I had occasionally. I 
suspect my internal ethernet controller making problems so for testing I used 
an usb ethernet connector. For now everything is fine. This time installation 
finished.

BTW: I was not aware that Guix reboot is a scheme command. I did Ctrl-Alt-Del 
instead.
Booting with grub failed then ;)

Thank you for your help
Enno

Re: Kernel panic while building VM

[Ludovic Courtès]

Hello,

Enrico Schwass  skribis:

>> Could you try again and report (1) what you did, (2) the
>> ‘operating-system’ configuration you used, and (3) the error messages
>> you see and when you see them?
>> 
>>> I will test the hardware with Guix 12 at the weekend
>> 
>> Please stick to 0.13.0.  0.12.0 is relatively old, so you’ll find that
>> many pre-built binaries are missing, not to mention many security fixes.
>
> I use the lightweight-desktop.scm just changed user name and partition setup. 
> Here are some screenshots

It’s hard to tell much here.  Is this happening with 0.13.0?  One of the
screenshots shows that Python was being built from source, which is
suspicious.

Thanks,
Ludo’.

Re: Kernel panic while building VM

[Myles English]

on [2017-06-20] at 17:31 Marius Bakke writes:

> Myles English <mylesengl...@gmail.com> writes:
>
>> Hello,
>>
>> Trying to build a VM I get a kernel panic.  Any idea why?
>>
>> Thanks,
>> Myles
>>
>> guix system vm-image --image-size=1G --fallback pim-server.scm
>>
>> `/gnu/store/gh9pvc82l21g0hz5108wk2ggwv0a72yc-guile2.2-gnutls-3.5.9/bin/gnutls-serv'
>>  -> 
>> `/fs/gnu/store/gh9pvc82l21g0hz5108wk2ggwv0a72yc-guile2.2-gnutls-3.5.9/bin/gnutls-serv'
>> `/gnu/store/gh9pvc82l21g0hz5108wk2ggwv0a72yc-guile2.2-gnutls-3.5.9/bin/psktool'
>>  -> 
>> `/fs/gnu/store/gh9pvc82l21g0hz5108wk2ggwv0a72yc-guile2.2-gnutls-3.5.9/bin/psktool'
>> `/gnu/store/gh9pvc82l21g0hz5108wk2ggwv0a72yc-guile2.2-gnutls-3.5.9/bin/ocsptool'
>>  -> 
>> `/fs/gnu/store/gh9pvc82l21g0hz5108wk2ggwv0a72yc-guile2.2-gnutls-3.5.9/bin/ocsptool'
>> ERROR: In procedure copy-file:
>> ERROR: In procedure copy-file: Success
>>
>> Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
>> [  236.784010] Kernel panic - not syncing: Attempted to kill init! 
>> exitcode=0x
>
> I've seen a similar failure when the disk image was too small to fit the
> system declaration. Do you get the same error with a larger image size?

That was it, thanks!

Myles

Re: Kernel panic while building VM

[Marius Bakke]

Myles English <mylesengl...@gmail.com> writes:

> Hello,
>
> Trying to build a VM I get a kernel panic.  Any idea why?
>
> Thanks,
> Myles
>
> guix system vm-image --image-size=1G --fallback pim-server.scm
>
> `/gnu/store/gh9pvc82l21g0hz5108wk2ggwv0a72yc-guile2.2-gnutls-3.5.9/bin/gnutls-serv'
>  -> 
> `/fs/gnu/store/gh9pvc82l21g0hz5108wk2ggwv0a72yc-guile2.2-gnutls-3.5.9/bin/gnutls-serv'
> `/gnu/store/gh9pvc82l21g0hz5108wk2ggwv0a72yc-guile2.2-gnutls-3.5.9/bin/psktool'
>  -> 
> `/fs/gnu/store/gh9pvc82l21g0hz5108wk2ggwv0a72yc-guile2.2-gnutls-3.5.9/bin/psktool'
> `/gnu/store/gh9pvc82l21g0hz5108wk2ggwv0a72yc-guile2.2-gnutls-3.5.9/bin/ocsptool'
>  -> 
> `/fs/gnu/store/gh9pvc82l21g0hz5108wk2ggwv0a72yc-guile2.2-gnutls-3.5.9/bin/ocsptool'
> ERROR: In procedure copy-file:
> ERROR: In procedure copy-file: Success
>
> Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
> [  236.784010] Kernel panic - not syncing: Attempted to kill init! 
> exitcode=0x

I've seen a similar failure when the disk image was too small to fit the
system declaration. Do you get the same error with a larger image size?


signature.asc
Description: PGP signature

Re: Kernel panic - not syncing: attempting to kill init! when booting GuixSD

[Quiliro]

I have had this same problem when garbage collecting on the root user. It 
happened to me twice. It was strange for me since I understood that Guix would 
NEVER remove any package that still had links to it.

What I did was try to boot with all entries presented on boot by GrUB. I 
usually found one that booted.

I am sorry I cannot reproduce this error since the 32 bit machine that I tryed 
garbage collecting previous generations on has died. I will test it on my other 
machines when I can manage to have a local substitute server to install offline 
from.


pgp2_9WtziEis.pgp
Description: OpenPGP cifera subskribo

Re: Kernel panic - not syncing: attempting to kill init! when booting GuixSD

[Christopher Baines]

On 28/05/17 16:49, Ludovic Courtès wrote:
> Hi Christopher,
> 
> Christopher Baines <m...@cbaines.net> skribis:
> 
>> So I deleted some system generations from one of my GuixSD systems, then
>> rebooted. Unfortunately, I can no longer get it to boot. I think the
>> latest system generation should work, and at least one of the previous
>> generations should work.
>>
>> Excluding the generations that I removed, the others don't boot. All I
>> can really gather so far is a call stack, and the message:
>>   Kernel panic - not syncing: Attempted to kill init!
> 
> Weird.  Is it because the root file system could not be found?  Or
> something else?  Like Ricardo wrote, could it be that the file system
> label changed or something?

Looking at the file system and configuration, it seems that this is
unlikely.

>> I'm going to try and make some time to see if I can get this system back
>> working again. I'm not sure how realistic this is, but I'm planning to
>> start by using the installation image, and somehow running  guix system
>> reconfigure.
> 
> I would suggest booting from an external medium such as the installation
> image, mounting the file system that holds /gnu/store, and inspecting
> there.
> 
> Also worth trying: you could edit the command line in the GRUB menu to
> have it refer to /var/guix/profiles/system-NNN-link, where NNN is the
> number of a previous generation known to be on disk.

I don't have the right cables to attempt to get a serial connection to
see what is going on in the early boot, so I tried running guix system
init from some GuixSD installation media. I'm glad to say that it worked :)

After running guix system init, I had a working system generation to
boot with.

I'll try to setup some kind of serial connection, so that I can attempt
to debug further if this happens again.

Thanks,

Chris




signature.asc
Description: OpenPGP digital signature

Re: Kernel panic - not syncing: attempting to kill init! when booting GuixSD

[Christopher Baines]

On 24/05/17 16:45, Ricardo Wurmus wrote:
> 
> Christopher Baines <m...@cbaines.net> writes:
> 
>> Excluding the generations that I removed, the others don't boot. All I
>> can really gather so far is a call stack, and the message:
>>   Kernel panic - not syncing: Attempted to kill init!
> 
> Has the label of your root partition changed?

I've just checked, and it doesn't seem to have changed.




signature.asc
Description: OpenPGP digital signature

Re: Kernel panic - not syncing: attempting to kill init! when booting GuixSD

[Ludovic Courtès]

Hi Christopher,

Christopher Baines <m...@cbaines.net> skribis:

> So I deleted some system generations from one of my GuixSD systems, then
> rebooted. Unfortunately, I can no longer get it to boot. I think the
> latest system generation should work, and at least one of the previous
> generations should work.
>
> Excluding the generations that I removed, the others don't boot. All I
> can really gather so far is a call stack, and the message:
>   Kernel panic - not syncing: Attempted to kill init!

Weird.  Is it because the root file system could not be found?  Or
something else?  Like Ricardo wrote, could it be that the file system
label changed or something?

> I'm uncertain that this is something I have done wrong, I'm pretty sure
> I was using the latest system generation when I ran guix gc, and I'm
> assuming that it is the garbage collection that has stopped things working.

It’s unlikely.  You could have run ‘guix’ with a wrong database location
(see ‘--localstatedir’ in the manual), but even that wouldn’t have
reclaimed store items used by the processes currently running.

> I'm going to try and make some time to see if I can get this system back
> working again. I'm not sure how realistic this is, but I'm planning to
> start by using the installation image, and somehow running  guix system
> reconfigure.

I would suggest booting from an external medium such as the installation
image, mounting the file system that holds /gnu/store, and inspecting
there.

Also worth trying: you could edit the command line in the GRUB menu to
have it refer to /var/guix/profiles/system-NNN-link, where NNN is the
number of a previous generation known to be on disk.

HTH!

Ludo’.

Re: Kernel panic - not syncing: attempting to kill init! when booting GuixSD

[Ricardo Wurmus]

Christopher Baines <m...@cbaines.net> writes:

> Excluding the generations that I removed, the others don't boot. All I
> can really gather so far is a call stack, and the message:
>   Kernel panic - not syncing: Attempted to kill init!

Has the label of your root partition changed?

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

Re: Kernel panic while installing GuixSD

[Kabelo Moiloa]

Could you elaborate, do you want me to write down the call trace? The last
things to be displayed for me are the call trace, some quartets of
hexadecimal numbers, and the hardware name.
On Tue, 26 Jan 2016 at 4:04 PM, Ludovic Courtès <l...@gnu.org> wrote:

> Hi,
>
> Kabelo Moiloa <moiloakab...@gmail.com> skribis:
>
> > I copied the installation image onto my USB flash drive. When I tried to
> > boot it, I got the following kernel panic.:
> > kernel panic-not syncing: VFS: unable to mount root fs on unknown block
> > (0,1).
>
> Could you report the error messages that show up before that one?
>
> It seems that the initialization code failed to locate the device that
> contains the installation image.
>
> TIA,
> Ludo’.
>