Kernel Panic during booting GuixSD

DoneSubmitted by white white.
Details
3 participants
  • Ludovic Courtès
  • Ricardo Wurmus
  • white white
Owner
unassigned
Severity
normal
W
W
white white wrote on 23 Jun 2017 16:25
(address . bug-Guix@gnu.org)
CAK_fBYzvWuZrN4WEFDuR7+xXh=hseuU3gnTVHZd1+TYYKwWMWA@mail.gmail.com
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.xzwhich is correctly downloaded for my system which has a 64bit cpu .this is my system configuration file : http://paste.lisp.org/display/349278#1I installed GuixSD two times on the system . First time I got this warning:
" warning: Sector 33 is already in use by the program `FlexNet'; avoidingit. This software may cause boot or other problems in future. Please askits 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: file
R
R
Ricardo Wurmus wrote on 25 Jun 2017 01:06
(name . white white)(address . whitewhitemanwhite@gmail.com)(address . bug-Guix@gnu.org)
87tw35kmt1.fsf@elephly.net
Hi,
Toggle quote (5 lines)> 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 notimpossible 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 ACAChttps://elephly.net
R
R
Ricardo Wurmus wrote on 25 Jun 2017 10:46
(name . white white)(address . whitewhitemanwhite@gmail.com)(address . 27460@debbugs.gnu.org)
87r2y8laj7.fsf@elephly.net
white white <whitewhitemanwhite@gmail.com> writes:
Toggle quote (9 lines)> 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. Inyour 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 ACAChttps://elephly.net
L
L
Ludovic Courtès wrote on 26 Aug 2017 16:18
control message for bug #27460
(address . control@debbugs.gnu.org)
87y3q68la9.fsf@gnu.org
tags 27460 moreinfo
L
L
Ludovic Courtès wrote on 1 Jan 2018 18:26
(address . control@debbugs.gnu.org)
87bmidze10.fsf@gnu.org
tags 27460 wontfixclose 27460
?
Your comment

This issue is archived.

To comment on this conversation send email to 27460@debbugs.gnu.org