--- Begin Message ---
Subject: |
Kernel panic after system reconfiguration |
Date: |
Wed, 3 Feb 2016 17:47:17 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0 |
Hi,
With no other changes I just ran guix pull and guix system reconfigure
on my MacBook2,1 which created an unbootable system.
After having completed the reconfiguration I tried to halt or reboot the
system but got this error message:
> error: connect: /var/run/shepherd/socket: file or directory does not exist
I did a hard shutdown and rebooted.
I've attached a picture of the kernel panic screen and here is my system
configuration:
http://paste.lisp.org/display/306452
The OS was quite bootable after my last reconfiguration on January 26.
Albin
albin-kernel-panic.jpg
Description: JPEG image
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#22548: Kernel panic after system reconfiguration |
Date: |
Fri, 05 Feb 2016 14:05:25 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
address@hidden (Ludovic Courtès) skribis:
> Alex Kost <address@hidden> skribis:
>
>> And as reported by several people on #guix (I count at least 4 including
>> me and Mark) a wrong swap device leads to a kernel panic if shepherd is
>> used as the init system.
>>
>> Until I realized that it was a wrong swap, I made bisecting on shepherd
>> to find out which commit introduced this bug. It gave me commit
>> 852341e¹: when I reconfigured my system (with a wrong swap) using
>> shepherd on this commit, I had a kernel panic, while with shepherd on
>> the previous commit the system booted successfully.
>>
>> ¹
>> http://git.savannah.gnu.org/cgit/shepherd.git/commit/?id=852341ed0c08941cbdd022135f8bef7be2d7ec54
>
> Ooooh, it took me a while but I see how this happens. This is because
> we start services directly from the config file, and anything that goes
> wrong there is uncaught, which leads to this:
>
> Service udev has been started.
> srfi-34(#<condition &action-runtime-error [service: #<<service> 184b150>
> action: start key: system-error arguments: ("swapon" "~S: ~A"
> ("/dev/disk/foobar" "No such file or directory") (2))] 1ea24c0>)
> [ 6.856167] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x00000100
> [ 6.856167]
> [ 6.856869] CPU: 0 PID: 1 Comm: shepherd Not tainted 4.4.1-gnu #1
> [ 6.857319] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
> rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
Commit 081bd3b fixes it. Commit 234ea8a defensively wraps all the
configuration file in ‘call-with-error-handling’, which spawns a REPL
upon error.
Thanks for the detailed investigation!
Ludo’.
--- End Message ---