From: Enrico Schwass <ennoausberlin@mac.com>
To: help-guix@gnu.org
Subject: Re: Kernel panic while building VM
Date: Tue, 20 Jun 2017 19:12:44 +0200 [thread overview]
Message-ID: <80CD6A63-9926-46E3-B40F-000036B58FB1@mac.com> (raw)
In-Reply-To: <87lgompq5b.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2537 bytes --]
Hello
since Guix 13 I have kernel panics during guix system init, too. It happens on my Intel J1900 fanless box. Dont know if its just overheating or if its a general problem with the libre kernel. I will test the hardware with Guix 12 at the weekend
Enno
>
> 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=0x00000000
> [ 236.784010]
> [ 236.786038] CPU: 0 PID: 1 Comm: init Not tainted 4.11.6-gnu #1
> [ 236.787333] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.10.2-0-g5f4c7b1-prebuilt.qemu-project.org 04/01/2014
> [ 236.789913] Call Trace:
> [ 236.790479] dump_stack+0x63/0x90
> [ 236.791228] panic+0xe4/0x22d
> [ 236.791908] do_exit+0xb45/0xb50
> [ 236.792637] ? wake_up_state+0x10/0x20
> [ 236.793466] do_group_exit+0x43/0xb0
> [ 236.794321] SyS_exit_group+0x14/0x20
> [ 236.795233] entry_SYSCALL_64_fastpath+0x1e/0xad
> [ 236.796355] RIP: 0033:0x5e6ed8
> [ 236.797035] RSP: 002b:00007ffe49d48f68 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
> [ 236.798684] RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00000000005e6ed8
> [ 236.800232] RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
> [ 236.801780] RBP: 00000000007ef7d0 R08: 00000000000000e7 R09: ffffffffffffffc8
> [ 236.803335] R10: 00000000000009d0 R11: 0000000000000246 R12: 00000000004cd850
> [ 236.804907] R13: 0000000000a80020 R14: 00000000014f95f0 R15: 0000000000000001
> [ 236.806815] Kernel Offset: 0x5000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
> [ 236.809175] ---[ end Kernel panic - not syncing: Attempted to kill
> init! exitcode=0x00000000
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 3795 bytes --]
next prev parent reply other threads:[~2017-06-20 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 16:42 Kernel panic while building VM Myles English
2017-06-20 17:12 ` Enrico Schwass [this message]
2017-06-21 10:28 ` Ludovic Courtès
2017-06-21 16:52 ` Enrico Schwass
2017-06-21 19:39 ` Ludovic Courtès
2017-06-21 20:57 ` Enrico Schwass
2017-06-20 17:31 ` Marius Bakke
2017-06-20 19:48 ` Myles English
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=80CD6A63-9926-46E3-B40F-000036B58FB1@mac.com \
--to=ennoausberlin@mac.com \
--cc=help-guix@gnu.org \
/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).