bug#27460: Kernel Panic during booting GuixSD

bug#27460: Kernel Panic during booting GuixSD

[white white]

[-- Attachment #1: Type: text/plain, Size: 792 bytes --]

Hi

When I boot the GuixSD I get this :

" end Kernel panic - not syncing: Attempted to kill init!
exitcode=0x00000000 "

I have downloaded this file : https://alpha.gnu.org/gnu/
guix/guixsd-usb-install-0.13.0.x86_64-linux.xz
which is correctly downloaded for my system which has a 64bit cpu .
this is my system configuration file : http://paste.lisp.org/display/
349278#1
I installed GuixSD two times on the system . First time I got this warning
:

" warning: Sector 33 is already in use by the program `FlexNet'; avoiding
it. This software may cause boot or other problems in future. Please ask
its authors not to store data in the boot track. "

So i used this code : "dd if=/dev/zero of=/dev/sda bs=512 count=1 seek=33"

And when I reinstalled the GuixSD I got no warning and no error .

[-- Attachment #2: Type: text/html, Size: 1216 bytes --]

bug#27460: Kernel Panic during booting GuixSD

[Ricardo Wurmus]

Hi,

> When I boot the GuixSD I get this :
>
> " end Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x00000000 "

do you have another machine where you could test the installation?
We’ve discussed this on IRC before and I ran out of ideas; it is not
impossible that this is a hardware problem of some kind.

Other ideas:

* What root file system do you use?  Could it be something that is not
  supported by our kernel?

* What kind of CPU do you use?

* Is there any more text in that kernel panic that might be interesting?

--
Ricardo

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

bug#27460: Kernel Panic during booting GuixSD

[Ricardo Wurmus]

white white <whitewhitemanwhite@gmail.com> writes:

> Yes , I will try on another machine.
> I use ext4.
> I use Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz.
> Maybe :
> " CPU: 0 PID: 1  Comm: init /not tainted 4.11.0-gnu #1"
> There is a "Call Trace" after that and a couple of information relating to
> it .
> I think it's because of the hardware .

One more thing you could try is to use a different kernel version.  In
your configuration you can change the “kernel” field, e.g. to

   (kernel linux-libre-4.1)

Make sure to include this line at the top:

   (use-package-modules linux)

With some luck this might get you further.

-- 
Ricardo

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