GNU bug report logs -
#27605
Lightweight desktop example fails to build with kernel panic
Previous Next
Reported by: Leo Famulari <leo <at> famulari.name>
Date: Fri, 7 Jul 2017 03:51:02 UTC
Severity: normal
Done: Leo Famulari <leo <at> famulari.name>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 27605 in the body.
You can then email your comments to 27605 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#27605
; Package
guix
.
(Fri, 07 Jul 2017 03:51:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Leo Famulari <leo <at> famulari.name>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Fri, 07 Jul 2017 03:51:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
[...]
registering closures...
populating...
creating FAT partition...
mkfs.fat 4.1 (2017-01-24)
mounting root partition...
[ 688.377705] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
installing bootloader...
/gnu/store/0g5bgkc757xmafxs2prjj896qpzj9wan-grub-efi-2.02/sbin/grub-install: error: /gnu/store/0g5bgkc757xmafxs2prjj896qpzj9wan-grub-efi-2.02/lib/grub/i386-pc/modinfo.sh doesn't exist. Please specify --target or --directory.
ERROR: In procedure scm-error:
ERROR: failed to install GRUB
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
[ 688.458461] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
[ 688.458461]
[ 688.459789] CPU: 0 PID: 1 Comm: init Not tainted 4.12.0-gnu #1
[ 688.460629] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.10.2-0-g5f4c7b1-prebuilt.qemu-project.org 04/01/2014
[ 688.462310] Call Trace:
[ 688.462857] dump_stack+0x63/0x82
[ 688.463785] panic+0xe4/0x22d
[ 688.464611] do_exit+0xae2/0xaf0
[ 688.465509] ? wake_up_state+0x10/0x20
[ 688.466330] do_group_exit+0x43/0xb0
[ 688.467147] SyS_exit_group+0x14/0x20
[ 688.467999] entry_SYSCALL_64_fastpath+0x1e/0xa9
[ 688.469144] RIP: 0033:0x5e6b98
[ 688.469902] RSP: 002b:00007ffe66065998 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
[ 688.471236] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00000000005e6b98
[ 688.472252] RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
[ 688.473413] RBP: 0000000000a51938 R08: 00000000000000e7 R09: ffffffffffffffc8
[ 688.475139] R10: 0000000000000ec0 R11: 0000000000000246 R12: 0000000000000001
[ 688.476422] R13: 0000000000a7f020 R14: 000000000352b700 R15: 0000000000000001
[ 688.477540] Kernel Offset: 0x37000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 688.479119] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
[ 688.479119]
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#27605
; Package
guix
.
(Fri, 07 Jul 2017 12:24:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 27605 <at> debbugs.gnu.org (full text, mbox):
Hi Leo,
Leo Famulari <leo <at> famulari.name> skribis:
> [...]
> registering closures...
> populating...
> creating FAT partition...
> mkfs.fat 4.1 (2017-01-24)
> mounting root partition...
> [ 688.377705] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
> installing bootloader...
> /gnu/store/0g5bgkc757xmafxs2prjj896qpzj9wan-grub-efi-2.02/sbin/grub-install: error: /gnu/store/0g5bgkc757xmafxs2prjj896qpzj9wan-grub-efi-2.02/lib/grub/i386-pc/modinfo.sh doesn't exist. Please specify --target or --directory.
> ERROR: In procedure scm-error:
> ERROR: failed to install GRUB
Did you pass --image-size? If not, it could be that the image size
estimate is slightly too small (see commit
a8ac4f081a9a679498ea42ccfe001f218bba3043).
The build log should contain something like:
creating ~a image of ~,2f MiB...
where ~a is “raw” or “qcow2” depending on the “guix system” command you
used.
Could you check what happens if you pass a --image-size argument bigger
than that?
Thanks,
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#27605
; Package
guix
.
(Fri, 07 Jul 2017 12:54:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 27605 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Fri, Jul 07, 2017 at 02:23:05PM +0200, Ludovic Courtès wrote:
> Did you pass --image-size? If not, it could be that the image size
> estimate is slightly too small (see commit
> a8ac4f081a9a679498ea42ccfe001f218bba3043).
>
> The build log should contain something like:
>
> creating ~a image of ~,2f MiB...
>
> where ~a is “raw” or “qcow2” depending on the “guix system” command you
> used.
>
> Could you check what happens if you pass a --image-size argument bigger
> than that?
I doubled it from ~10 GiB to ~20 GiB:
> creating qcow2 image of 19359.59 MiB...
This example template uses EFI, which I'm not that familiar with. But I
suspect something about the bootloader or filesystems configuration is
wrong.
From 'gnu/system/examples/lightweight-desktop.tmpl':
;; Use the UEFI variant of GRUB with the EFI System
;; Partition on /dev/sda1.
(bootloader (grub-configuration (grub grub-efi)
(device "/dev/sda1")))
;; Assume the target root file system is labelled "my-root".
(file-systems (cons* (file-system
(device "my-root")
(title 'label)
(mount-point "/")
(type "ext4"))
(file-system
;; Specify partition here since FAT
;; labels are currently unsupported.
(device "/dev/sda1")
(mount-point "/boot/efi")
(type "vfat"))
%base-file-systems))
[signature.asc (application/pgp-signature, inline)]
Reply sent
to
Leo Famulari <leo <at> famulari.name>
:
You have taken responsibility.
(Fri, 07 Jul 2017 13:22:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Leo Famulari <leo <at> famulari.name>
:
bug acknowledged by developer.
(Fri, 07 Jul 2017 13:22:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 27605-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Fri, Jul 07, 2017 at 08:53:37AM -0400, Leo Famulari wrote:
> On Fri, Jul 07, 2017 at 02:23:05PM +0200, Ludovic Courtès wrote:
> > Did you pass --image-size? If not, it could be that the image size
> > estimate is slightly too small (see commit
> > a8ac4f081a9a679498ea42ccfe001f218bba3043).
> >
> > The build log should contain something like:
> >
> > creating ~a image of ~,2f MiB...
> >
> > where ~a is “raw” or “qcow2” depending on the “guix system” command you
> > used.
> >
> > Could you check what happens if you pass a --image-size argument bigger
> > than that?
>
> I doubled it from ~10 GiB to ~20 GiB:
>
> > creating qcow2 image of 19359.59 MiB...
>
> This example template uses EFI, which I'm not that familiar with. But I
> suspect something about the bootloader or filesystems configuration is
> wrong.
Actually, false alarm! After increasing the image size to 20 GiB, I
missed the messages about being out of space. Sorry for the noise!
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#27605
; Package
guix
.
(Fri, 07 Jul 2017 13:41:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 27605 <at> debbugs.gnu.org (full text, mbox):
Leo Famulari <leo <at> famulari.name> skribis:
> On Fri, Jul 07, 2017 at 02:23:05PM +0200, Ludovic Courtès wrote:
>> Did you pass --image-size? If not, it could be that the image size
>> estimate is slightly too small (see commit
>> a8ac4f081a9a679498ea42ccfe001f218bba3043).
>>
>> The build log should contain something like:
>>
>> creating ~a image of ~,2f MiB...
>>
>> where ~a is “raw” or “qcow2” depending on the “guix system” command you
>> used.
>>
>> Could you check what happens if you pass a --image-size argument bigger
>> than that?
>
> I doubled it from ~10 GiB to ~20 GiB:
>
>> creating qcow2 image of 19359.59 MiB...
>
> This example template uses EFI, which I'm not that familiar with. But I
> suspect something about the bootloader or filesystems configuration is
> wrong.
>
> From 'gnu/system/examples/lightweight-desktop.tmpl':
>
> ;; Use the UEFI variant of GRUB with the EFI System
> ;; Partition on /dev/sda1.
> (bootloader (grub-configuration (grub grub-efi)
> (device "/dev/sda1")))
Oh right, so the failure is probably unrelated to the image-size
estimate.
Marius, any ideas? :-)
https://bugs.gnu.org/27605
Thanks,
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#27605
; Package
guix
.
(Fri, 07 Jul 2017 15:18:01 GMT)
Full text and
rfc822 format available.
Message #22 received at 27605-done <at> debbugs.gnu.org (full text, mbox):
Leo Famulari <leo <at> famulari.name> skribis:
> On Fri, Jul 07, 2017 at 08:53:37AM -0400, Leo Famulari wrote:
>> On Fri, Jul 07, 2017 at 02:23:05PM +0200, Ludovic Courtès wrote:
>> > Did you pass --image-size? If not, it could be that the image size
>> > estimate is slightly too small (see commit
>> > a8ac4f081a9a679498ea42ccfe001f218bba3043).
>> >
>> > The build log should contain something like:
>> >
>> > creating ~a image of ~,2f MiB...
>> >
>> > where ~a is “raw” or “qcow2” depending on the “guix system” command you
>> > used.
>> >
>> > Could you check what happens if you pass a --image-size argument bigger
>> > than that?
>>
>> I doubled it from ~10 GiB to ~20 GiB:
>>
>> > creating qcow2 image of 19359.59 MiB...
>>
>> This example template uses EFI, which I'm not that familiar with. But I
>> suspect something about the bootloader or filesystems configuration is
>> wrong.
>
> Actually, false alarm! After increasing the image size to 20 GiB, I
> missed the messages about being out of space. Sorry for the noise!
So the problem is that the estimate was too small, right?
It would be awesome if you could fiddle with the heuristics in there to
see what would work. :-)
Thanks,
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#27605
; Package
guix
.
(Fri, 07 Jul 2017 16:33:01 GMT)
Full text and
rfc822 format available.
Message #25 received at 27605-done <at> debbugs.gnu.org (full text, mbox):
On Fri, Jul 07, 2017 at 05:16:54PM +0200, Ludovic Courtès wrote:
> > Actually, false alarm! After increasing the image size to 20 GiB, I
> > missed the messages about being out of space. Sorry for the noise!
>
> So the problem is that the estimate was too small, right?
No, the problem was that I forgot about the estimator and tried to use
10 GiB, which was too small :)
> It would be awesome if you could fiddle with the heuristics in there to
> see what would work. :-)
I just tried the estimator and it worked fine.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#27605
; Package
guix
.
(Fri, 07 Jul 2017 17:52:02 GMT)
Full text and
rfc822 format available.
Message #28 received at 27605-done <at> debbugs.gnu.org (full text, mbox):
Leo Famulari <leo <at> famulari.name> skribis:
> On Fri, Jul 07, 2017 at 05:16:54PM +0200, Ludovic Courtès wrote:
>> > Actually, false alarm! After increasing the image size to 20 GiB, I
>> > missed the messages about being out of space. Sorry for the noise!
>>
>> So the problem is that the estimate was too small, right?
>
> No, the problem was that I forgot about the estimator and tried to use
> 10 GiB, which was too small :)
>
>> It would be awesome if you could fiddle with the heuristics in there to
>> see what would work. :-)
>
> I just tried the estimator and it worked fine.
Perfect. :-)
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 05 Aug 2017 11:24:03 GMT)
Full text and
rfc822 format available.
This bug report was last modified 6 years and 264 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.