unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>,
	54651@debbugs.gnu.org
Subject: bug#54651: Guix pull failing on ARM 32bit with "Please report the COMPLETE output above by email"
Date: Mon, 23 May 2022 16:10:04 +0200	[thread overview]
Message-ID: <4b1c3ca59539d07365fce79b00563986cc0846ae.camel@telenet.be> (raw)
In-Reply-To: <20220523154040.35996f59@primarylaptop.localdomain>

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

Denis 'GNUtoo' Carikli schreef op ma 23-05-2022 om 15:40 [+0200]:
> Hi,
> 
> I've now made some free space. So we have:
> - 1GiB of RAM and 16GiB of swap:
>   > # cat /proc/swaps 
>   >
> Filename				Type		Size	
> 	Used		Priority
>   > /dev/mmcblk0p1                         
> partition	16777212	16384		-2

Could you check if it OOMs (with "sudo dmesg")?
There were some problems in the past (maybe present too?) on i?86 with
too much memory usage,

Greetings,
Maxime

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-05-23 14:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 12:15 bug#54651: Guix pull failing on ARM 32bit with "Please report the COMPLETE output above by email" Denis 'GNUtoo' Carikli
2022-04-05 15:02 ` Denis 'GNUtoo' Carikli
2022-05-18 13:47   ` Denis 'GNUtoo' Carikli
2022-05-23 13:40 ` Denis 'GNUtoo' Carikli
2022-05-23 14:10   ` Maxime Devos [this message]
2022-05-23 14:22     ` raingloom
2022-05-23 17:30     ` Denis 'GNUtoo' Carikli
2022-05-23 18:27       ` Maxime Devos
2022-05-23 19:08       ` Denis 'GNUtoo' Carikli
2022-05-23 22:18         ` Denis 'GNUtoo' Carikli
2022-05-24  8:34         ` Maxime Devos

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=4b1c3ca59539d07365fce79b00563986cc0846ae.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=54651@debbugs.gnu.org \
    --cc=GNUtoo@cyberdimension.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).